Amazon CloudFront has just announced several new features
(specific to CloudFront download distributions) that help customers deliver
their full website via CloudFront. Customers
asked to support delivery of their entire website containing static objects,
dynamic content, or a mixture of the two. With these features, the goal is to
make it as simple as possible for customers to use CloudFront to speed up
delivery of their entire dynamic website they run in Amazon EC2/ELB (or
third-party origins), without needing to worry about which URLs should point to
CloudFront and which ones should go directly to the origin.
The set of features include:
The set of features include:
The ability to specify multiple origin servers
The ability to specify multiple origin servers includes a
default origin and available for a CloudFront download distribution. This is
useful when customers want to use different origin servers for different types
of content. For example, an Amazon S3 bucket can be used as the origin for your
static objects and an Amazon EC2 instance as the origin for your dynamic
content, all fronted by the same CloudFront distribution domain name. Note that
non-AWS origins are also permitted.
The ability to include query string parameters.
Customers will have a
switch to turn query strings 'on' or 'off'. When turned off, CloudFront's
behavior will be the same as today - i.e., CloudFront will not pass the query
string to the origin server nor include query string parameters as a part of
the object's cache key. And when query strings are turned on, CloudFront will
pass the full URL (including query args) to the origin server and also use the
full URL to uniquely identify an object in the cache.
The ability to configure cache behaviors based on URL path patterns.
Each URL path pattern
will include a set of cache behaviors associated with it. These cache behaviors
include the target origin, a switch for query strings to be on/off, a list of
trusted signers for private content, the viewer protocol policy, and the minTTL
that CloudFront should apply for that URL path pattern. For example, a path
pattern "*.jpg" could have an Amazon S3 bucket as the origin server,
query strings set to false, trusted signers disabled, viewer protocol policy of
'allow-all' and a minTTL of 3600. Then, a second path pattern "*.php"
could have example.com set
as the origin server, query strings set to true, trusted signers enabled with a
list of valid signers, viewer protocol policy of 'https-only' and a minTTL of
0. Note that the URL path patterns should be listed in the order that
CloudFront should process for matching the request URL. There must also be a
default cache behavior that CloudFront should use when none of the URL path
patterns are a match.
Note that the features above are specific to download
distributions only. CloudFront functionality for streaming distributions
remains unchanged.
The latest version of CloudBerry Explorer comes with
full support of aforementioned features. To take advantage of the new features
you will have to select advanced configuration option
there is a special step for specifying multiple origins
you have a choice between Amazon S3 and custom origin. for s3 origin you can also
enable Private Content and specify the origins access identity.
For custom origin you specify DNS name and other parameters
There is another step for configuring the Default Cache Behavior
And yet another step for custom Cache Behavior
Click Add to create a Pattern
+++
Note: this post applies to CloudBerry
Explorer 3.4 and later.
As always we would be happy to hear your feedback and you
are welcome to post a comment.
CloudBerry
S3 Explorer is a Windows freeware product that helps managing Amazon S3 storage and CloudFront . You can
download it at http://www.cloudberrylab.com/free
CloudBerry
S3 Explorer PRO is a Windows program that helps managing Amazon S3 storage and CloudFront . You can
download it at http://www.cloudberrylab.com/pro It is priced at $39.99
Want to get CloudBerry Explorer PRO for FREE? Make a blog
post about us!
Posts
