Amazon's file storage service is called S3 (or
Simple Storage Service
). Files stored on S3 can be downloaded directly from S3 servers to your end user's browser. Amazon has a
content delivery network
which can take your files stored in S3 and deliver them to your end user via their 14 servers geographically separated around the globe.
Recently Rackspace has entered this market with a file storage service called
. The name is uninspired but certainly readily understood. Instead of creating their own content delivery network, as Amazon did, Rackspace partnered with the well-known CDN provider
. Files stored in Rackspace Cloud Files can be delivered via the Limelight CDN. This is exciting because
Limelight has 60 edge locations compared to Amazon's 14
. I believe that Rackspace provide
service rather than
Both Amazon and Rackspace offer file storage at 15 cents per gigabyte. You get a better deal with Amazon on traffic, which charges 17 cents/GB. Rackspace charges 22 cents/GB. Interestingly, both Amazon and Rackspace don't charge any extra to deliver your files via the CDN. However with Amazon, you are charged for traffic between S3 and their Cloudfront servers. That means that if someone downloads a file from Cloudfront, you may be charged twice: once for the traffic between S3 to Cloudfront, and then again from Cloudfront to the end user. If the file is already cached on hand at the Cloudfront edge location, then you are only charged for traffic from Cloudfront to the end user. At some point the cached file at the Cloudfront edge server will expire and further requests will prompt that edge server to retrieve an updated version from S3. Rackspace, on the other hand, doesn't charge you for any bandwidth usage for file transfer between their Cloud File servers and Limelight.
Amazon allows you to have files hosted on S3 and Cloudfront to look like they are hosted on your own domain name. You just need to add a
CName directive to the DNS zone for your domain name
that points to the appropriate bucket in S3/Cloudfront. Rackspace doesn't support CName redirects for your Cloud File storage.
Amazon allows you to serve files to your end user via SSL. This is important if you are hosting graphics for use on SSL encrypted web pages/sites. If your cloud host cannot do this, your web page will not be fully SSL'd and IE users will get the irritating warning that the page contains secure and non-secure items. Amazon will not allow you to deliver files via SSL on your CName domain name. To reference a file stored on S3 via SSL, the URL should be formatted as follows: https://s3.amazonaws.com/bucket-name/key-name Note that files delivered via SSL this way will be served from S3 not CloudFront. Rackspace does not support delivery of content via SSL, as reported to me by a Rackspace salesperson via chat. I also chatted with a Limelight salesperson who said that it is supported. He gave me the number for a person at Rackspace who I called and was friendly and helpful. She confirmed that Rackspace's solution out-of-the-box cannot deliver content via SSL. However she was going to check with some engineers to see if anything can be done to enable SSL delivery. UPDATE: The Rackspace solution consultant emailed to confirm that there is not a way to deliver images via SSL in CloudFiles.
Amazon has a more mature and affordable cloud storage service. However Rackspace, partnered with Limelight, is a player to watch especially if they can provide CName and SSL. At that point Rackspace's higher bandwidth cost may be worth considering. If you are hosting larger files that do not require SSL and speed is an issue, going with Rackspace is a better option now because you can deliver via Limelight and not have to pay double bandwidth charges that you would be charged with Cloudfront/S3.
Other cloud storage providers
- They will only take you on as a customer if you host more than 1TB of data.