Cyberduck Mountain Duck CLI

#3190 closed enhancement (wontfix)

Multiple Cloudfront distributions

Reported by: dkocher Owned by: dkocher
Priority: low Milestone:
Component: s3 Version: 3.2
Severity: minor Keywords:
Cc: Architecture: Intel
Platform: Mac OS X 10.6


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.

Change History (3)

comment:1 Changed on Jan 16, 2010 at 5:40:33 PM by dkocher

	From: 	James Murty <>
	Subject: 	[JetS3t Users] Re: Amazon CloudFront support
	Date: 	26. November 2008 00:26:12 MEZ

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.

comment:2 Changed on Jan 16, 2010 at 5:41:41 PM by dkocher

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

comment:3 Changed on Jul 13, 2010 at 10:05:23 AM by dkocher

  • Architecture set to Intel
  • Platform set to Mac OS X 10.6
  • Resolution set to wontfix
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.