We use Amazon CloudFront to serve our static CSS and JS for dotspots.com. It's a fantastic and cheap pay-as-you-go CDN.<p>My only beefs:<p>1. Still no support for a root index.html (ie: serving the / URL from a domain) in either S3 or CloudFront, meaning you can't host a static site entirely on CloudFront.<p>2. No support in CloudFront for origin servers other than S3. Not a big deal, but CloudFront is so convenient that I'd like to stick it in front of more dynamic content as well.
<a href="http://aws.amazon.com/cloudfront/#details" rel="nofollow">http://aws.amazon.com/cloudfront/#details</a><p><pre><code> By default, files delivered through Amazon CloudFront are
publicly readable by anyone on the Internet. However, if you
require greater control over who can download or stream your
files, you can use Amazon CloudFront’s private content feature.
When this option is enabled, Amazon CloudFront will only deliver
files or stream media when you say it is okay to do so by
securely signing your requests. There is no additional charge
for using the private content feature.
</code></pre>
I don't get it, signed requests? But private CDN sounds very good.