Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiple Cloudfront distributions #3190

Closed
cyberduck opened this issue May 13, 2009 · 2 comments
Closed

Multiple Cloudfront distributions #3190

cyberduck opened this issue May 13, 2009 · 2 comments
Assignees
Labels
enhancement low priority s3 AWS S3 Protocol Implementation wontfix

Comments

@cyberduck
Copy link
Collaborator

@dkocher created the issue

There is currently no support to configure multiple cloudfront distributions for a given bucket. But I see no reason why this would be needed. Comment and vote for this if you do not agree.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

	From: 	James Murty <james@misterm.org>
	Subject: 	[JetS3t Users] Re: Amazon CloudFront support
	Date: 	26. November 2008 00:26:12 MEZ
	To: 	jets3t-users@googlegroups.com
	Reply-To: 	jets3t-users@googlegroups.com

I suppose you might gain an advantage having multiple distributions for a
single bucket if you serve pages with many components to web browsers that
limit the number of simultaneous connections per site. I believe that many
browsers do this, some with as few as 4 connections per site. If you serve a
page with many images for example, the connection restrictions may prevent
the browser from using all the available bandwidth to load the page.

People sometimes use multiple CNAMEs to work around per-site restrictions,
and you can use this approach with CloudFront's CNAME support as well, but
by setting up multiple distributions you could achieve the same thing
without having to set up the CNAMEs or worry about DNS stuff at all.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

We du support the configuration of both a single streaming and basic distribution per bucket. See #4069.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement low priority s3 AWS S3 Protocol Implementation wontfix
Projects
None yet
Development

No branches or pull requests

2 participants