Cyberduck Mountain Duck CLI

Version 29 (modified by dkocher, on Nov 16, 2010 at 5:58:39 PM) (diff)

--

Cyberduck Help / Howto / Amazon CloudFront Support

The user interface supports one basic and one streaming distribution configuration per bucket. You can enable cloud front distribution using File → Info → Distribution. You must signup for Amazon CloudFront first. Make sure your objects in the bucket you want to enable distribution for are world readable. In File → Info → Permissions give READ permission to Everyone (http://acs.amazonaws.com/groups/global/AllUsers).

No image "CloudFront configuration.png" attached to help/en/howto/cloudfront

Multiple CNAMEs for CloudFront distribution

Using File → Info → Distribution you can enter multiple CNAMEs for your bucket distribution. The hostnames must be space delimited.

Basic (HTTP) Distributions

Used to serve static content.

Streaming (RTMP) Distributions

Used to serve media using a streaming protocol.

Custom Origin (HTTP/HTTPS) Distributions

A custom origin is an origin server that isn't hosted on Amazon S3. The origin server holds the original, definitive versions of your content. You can connect to any server and configure it as an origin server for content distribution with Amazon CloudFront.

You need the latest snapshot build for this feature.

Playback Configuration

Copy the RTMP URL for a given file in a bucket with a streaming distribution enabled is displayed in the Info window Distribution (CDN) tab with Streaming (RTMP) selected as the delivery method. Where to put the URL depends on the client player you are using.

Deployment Status

Upon changing configuration parameters of a distribution configuration, the settings are not distributed immediatly in the CDN. While the deployment is in progress (which can take up to 15 minutes), the status In Progress is displayed. The updates are fully propagated throughout the CloudFront system when the distribution's state switches from In Progress to Deployed.

CloudFront Access Logging

When this option is enabled in the File → Info panel of a bucket, access logs are written to <bucketname>/logs. The changes to the logging configuration take effect within 12 hours. The logging option is supported for both standard and streaming distributions.

Default Root Object

You can assign a default root object to your HTTP or HTTPS distribution. This default object will be served when Amazon CloudFront receives a request for the root of your distribution – i.e., your distribution’s domain name by itself.

When you define a default root object, a user request that calls the root of your distribution returns the default root object. For example, if you designate the file index.html as your default root object, a request for http://d604721fxaaqy9.cloudfront.net/ returns http://d604721fxaaqy9.cloudfront.net/index.html.

Object Invalidation

Invalidation is one way to remove a distribution object from an edge server cache before the expiration setting on the object's header. Invalidation clears the object from the edge server cache, and a subsequent request for the object will cause CloudFront to return to the origin to fetch the latest version of the object.

You need the latest snapshot build for this feature.

References

Attachments (3)

Download all attachments as: .zip

swiss made software