Expanding the Cloud: Amazon CloudFront

| | Comments (19) | TrackBacks (4)

Today marks the launch of Amazon CloudFront, the new Amazon Web Service for content delivery. It integrates seamlessly with Amazon S3 to provide low-latency distribution of content with high data transfer speeds through a world-wide network of edge locations. It requires no upfront commitments and is a pay-as-you-go service in the same style as the other Amazon Web Services.

Amazon CloudFront has been designed to be fast; the service will cache copies of the content in edge locations close to the end-user's location, significantly lowering the access latency to the content. High sustainable data transfer rates can be achieved with the service especially when distributing larger objects.

Amazon CloudFront will be useful for many different application scenarios such as giving your customers low-latency access to popular objects and protecting your site from popularity surges; other popular examples are low-cost delivery of rich media and sustainable fast transfer rates for software distributions.

See also the posting on the AWS Developer weblog and at Rightscale.

Amazon CloudFront

Seamless integration

A content delivery service that would extend Amazon S3 has been something that is very high on the wish list of our customers. They were already successfully using Amazon S3 for some of their content distribution needs, but many wanted the choice to do so with even lower latency and with higher data transfer rates to any place in the world.

Customers really appreciate the scalability, reliability and cost-effectiveness of Amazon S3 and the fact that it integrates so easily with Amazon EC2. Amazon CloudFront builds further on that seamless integration by making it really simple to distribute Amazon S3 content world-wide. The combination of the two services is really powerful: Amazon S3 will give you durable storage of your data, and the network of edge locations on three continents used by the Amazon CloudFront will deliver the content to your customers with low latency from the most appropriate location.

The network of edge locations

To ensure low-latency delivery, Amazon CloudFront uses a network of edge locations world-wide:

  • United States: Ashburn (VA), Dallas/Fort Worth, Los Angeles, Miami, Newark, Palo Alto, Seattle and St. Louis
  • Europe: Amsterdam, Dublin, Frankfurt and London
  • Asia: Hong Kong and Tokyo

These edge locations work together to direct customers' requests to the edge location that can provide the response with the lowest latency.

Simplicity

Because Amazon CloudFront follows the core principles of all Amazon Web Services it is a unique content delivery service. The simplicity in getting started has been described by many of our early customers as a very important feature.

Using Amazon CloudFront is dead simple:

  1. Put your objects in an Amazon S3 bucket.
  2. Call the CreateDistribution API with the name of the S3 bucket, which will return your distribution's domain name.
  3. Use the new domain name in urls on your web or in your application. Whenever these urls are accessed CloudFront will determine the optimal edge location from where to serve your content.

Many of our private beta customers have reported that it only took them 10-15 minutes from the moment that they first signed up for the service to the moment that Amazon CloudFront was distributing their content.

The second Amazon Web Services principle that sets Amazon CloudFront apart is that no upfront commitments are necessary and you only pay for what you have used. There are no upfront fees or high volume requirements and no negotiations are necessary because we have published low prices from the start. This brings content delivery in the hands of all businesses, and you can exploit the benefits of Amazon's world-wide network of edge locations, regardless of whether you are a highly popular website, a small blog, a complex enterprise application or a developer doing some prototyping.

Tools such as S3Fox have support for Amazon CloudFront built-in such that if you want to avoid any programming you can immediately start exploiting world-wide, low-latency content delivery.

A core distributed systems component

It is not uncommon to think about a service for content delivery such as Amazon CloudFront only in the context of media distribution for web sites, but it actually plays a more fundamental role.

There are two main technology components to such a service; the first is intelligent request routing, which routes requests to the location that can best serve the user given a series of requirements and the status of the network. The second technology component is that of object caching, which is a fundamental building block in both operating systems and in distributed systems.

For example your operating system will have a file cache, where it will store popular, recently-accessed files in memory to provide much faster access and greater throughput. Without a file cache your whole computer would appear much slower as all work would happen at the speed of the disk instead of memory.

Caching is an essential technique that is used to make sure that components can operate at the fastest speed possible, to overcome the performance differences that exist in systems. For example CPU's have caches that are much faster than memory, memory works as caches for disks, local disks can function as caches for remote disks, etc.

In distributed systems caching is primarily used to provide fast access to popular objects that are located in remote storage servers. These systems of caching servers often cooperate to create massive aggregate world-wide capacity to provide low latency access. And by using globally decentralized cache servers for distribution, very high data transfer speed can be achieved.

Caching technology has long been the center piece of computer systems research and in Amazon CloudFront we use the type of highly advanced algorithms for reliability and scale that you have come to expect from our Amazon services.

Many of our customers will look to Amazon CloudFront for rock solid content distribution for websites, but its application is not limited to that. Developers can easily integrate the service into their desktop and server applications and benefit from the advanced routing and caching that Amazon CloudFront offers. For example enterprise style applications such as NASDAQ's Market Replay application are ideal candidates to integrate Amazon CloudFront to provide low latency access to popular market data while reducing the cost of data transfers.

Graphic by Renato Valdés Olmos of Postmachina

4 TrackBacks

Listed below are links to blogs that reference this entry: Expanding the Cloud: Amazon CloudFront .

TrackBack URL for this entry: http://mt.vogels.net/mt-tb.cgi/129

The team from Amazon Web Services (AWS) came to Toronto (at the MaRS Building)to show us their stuff, and demo’s from some local folks showing the “what”, “where”, and “how” to their use of  AWS in real life. ... Read More

» Brian McKinney had this to say from Reframe It -- It's Your Web, Speak Up, Give It Context

Here is another great service from Amazon. We could move images and other static assets to this for a better end user experience. Read More

Another remarkable day for Amazon Web Services as Werner Vogels, CTO - Amazon.com, launched the much anticipated CDN solution to the public after two months of announcement. Amazon AWS Amazon CloudFront Aptly named Amazon CloudFront, the beta version ... Read More

Schon bisher haben Firmen die Amazon S3 Storage Cloud für die Auslieferung von Bildern und Downloads genutzt. Allerdings hatte S3 im vergleich zu den anderen kommerziellen Content Delivery/Distribution Networks einen Performance Nachteil: wenn man ein CDN Read More

19 Comments

This is excellent Werner. Nice to see Amazon setting the tone for the Cloud Computing market.

Evan said:

I was surprised not to see Chicago or Atlanta on your list of edge locations. I was under the impression that either was a bigger hub than Ashburn or St Louis.

Having lived a few years in Nashville, I know all my traffic routes to Atlanta (even if the servers are in downtown Nashville). Comcast pipes it all down there over AT&T.

Are you planning on adding additional edge locations down the road?

Nubeblog said:

It looks really cool, and it was something we miss in the infraestructure.

What about Australia and New Zeland? They really can take big advantage of CloudFront!

James Grid
http://nubeblog.com

DivineOracle said:

I think their services can be enhanced further by embedding a more efficient file transfer protocol in their network infrastructure eg Rocketstream file transfer protocol (www.rocketstream.com)

DivineOracle

Saurabh said:

We have added support for CloudFront in Bucket Explorer. A beta, which supports CloudFront distributions can be downloaded from http://www.bucketexplorer.com/ or http://www.bucketexplorer.com/documentation/cloudfront--amazon-cloudfront.html

Saurabh

We have been testing CloudFront a bit today -- it is the easiest CDN we have seen. Our servers are in US, it looks like for our European users it would be 140 ms vs 20 ms difference when accesing static files ;-)

regards - michal

Good work! Nice to see that you guys are paying attention to Europe and Asia too! Then again that would be the purpose of an edge of internet service...

Max said:

Do you think that Hong Kong can be OK for new zealand & australia?

James said:

Cool, took me about 15 mins to read the docs & migrate to cloudfront. Another 20 mins to tweak my site to correctly read images from the new domain name & I’m done. Bad news is, being in Australia it looks like the closest node is still in the US (LA). Good news I’m getting massive speed improvements. Consistently x2 as fast or more than non-CDN speeds!

Amazon’s costs and negligible to me. I host in Australia and we always go over our included bandwidth at some at $ 3.3 / GB that’s some expensive excess data charges. I’ve been using S3 to serve almost all our image file to avoid some of the bandwidth cost, but I haven’t been happy with S3 speed at this point. This CDN really makes a big difference to me. I’m happy to migrate most of our remaining files across. Awesome work Amazon, fantastic integration with S3 - thanks!

reomtrexows said:

Блог интересный и полезный. Разместите все-таки информацию о donations (денежных перечислений от посетителей блога). Можно указать электронные кошельки или sms копилку. Я бы перечислила.

sam lessin said:

drop.io recently ditched our last hardware and went 100% into the amazon cloud (http://drop.io/blog) - and we can't wait to try this out -- thanks for all the hard work by the Amazon team, we are believers (to say the least)

ender said:

how does this compare to akamai?

Randall said:

Exciting news! Been waiting for something like this for a while.

Thejesh GN said:

So HongKong is the nearest node to India. I was expecting Singapore as India ( most of south India) has direct pipe connection to Singapore.

When can we expect next list of Nodes?

Thejesh GN said:

So HongKong is the nearest node to India. I was expecting Singapore as India ( most of south India) has direct pipe connection to Singapore.

When can we expect next list of Nodes?

Fagin said:

I have'nt got a Visa or Maestro card, any chance of offering the cloud with solo card support.

Ian said:

Does the new offering have referer checking support so we can stop hotlinking?

Sachin said:

It looks cool and the simplicity of CloudFront is what excites me.

Well done Werner, this is a service long awaited. Just as a point, do you actually use Content Delivery Networks (CDNs) to do this or did amazon use its own infrastructure?

About this Entry

This page contains a single entry by Werner Vogels published on November 17, 2008 10:00 PM.

Using the Cloud to build highly-efficient systems was the previous entry in this blog.

Expanding the Cloud: Amazon EC2 in Europe is the next entry in this blog.

Find recent content on the main index or look in the archives to find all content.