A few months ago I talked about our plans to create and offer a service for content delivery. That service is called Amazon CloudFront and it is ready now!

Like all of our other services, CloudFront was designed with ease of use in mind from the very beginning. There are no minimum usage commitments, no monthly fees, and no need to even talk to us. Here’s what you do:

Sign up for CloudFront. Put your most frequently accessed static content into an Amazon S3 bucket and mark it as publicly readable. Create a new CloudFront Distribution using a single REST-style POST call. Capture the domain name returned by the call. Generate fresh URLs for your content using the domain name from step 3 and hand them out. By using our CNAME support you can even make the content appear as if it is coming from your own domain. You can associate up to 10 CNAMEs with each distribution.

CloudFront will take care of the rest. Requests originating anywhere in the world will be routed to one of 14 edge locations (8 in the United States, 4 in Europe, and 2 in Asia). If the content isn’t already present at a particular edge location it will be fetched from S3 and cached at the edge.

You will be charged based on the number of requests that you make and the amount of data that you transfer. Pricing is covered in depth on the detail page. Because our costs vary by location, pricing for data served from edge locations outside of the US varies, and is currently slightly higher. You will also pay the usual S3 price for the “origin fetch” which take place when a requested object is transferred from S3 to an edge location, and for storage of the object in S3.

We are looking forward to seeing how this is put to use. It is certainly going to be used to host software downloads, frequently accessed website components, and media files. However, as is often the case with these new services, developers will find new and unique ways to put it to use before too long.

Our friends across the lake at Smartsheet have put together a nice worksheet which documents and generalizes the work that they did to support CloudFront in their own product.

Remarkably enough, parts of that website are already served up from CloudFront! You can use this worksheet to assign tasks to your developers, review the status of the tasks, and much more.

We’ve got plenty of CloudFront documentation including a Getting Started Guide, a Developer Guide, an FAQ, and even a Quick Reference Card.

Tool and library vendors have been working to support CloudFront in their products. I’ll update this post as I learn more.

Updates:

— Jeff;