When to use Amazon Cloudfront or S3?

Amazon CloudFront is some kind of Content Delivery Network (CDN), that takes its data from S3. What actually does is replicate the S3 data in different locations so that When end users request an object using this domain name, they are automatically routed to the nearest edge location for high performance delivery of your content. ( Amazon ) That's the main difference, and you take advantage of it when your user base is "spread around the world".

So If your user base is localized, you won't see too much difference working with S3 or CloudFront (but you have to choose the right location for your S3 bucket: US, EU, APAC) If your user base is spread, CloudFront should be a better option Another difference is that CloudFront allows you to set different domain aliases for your CloudFront distribution: You can have for example d1.mystatics. Com d2.mystatics. Com and d3.mystatics.Com pointing to the same CloudFront distribution, allowing parallel downloads ( Google ).

Amazon CloudFront is some kind of Content Delivery Network (CDN), that takes its data from S3. What actually does is replicate the S3 data in different locations, so that... When end users request an object using this domain name, they are automatically routed to the nearest edge location for high performance delivery of your content. (Amazon) That's the main difference, and you take advantage of it when your user base is "spread around the world".So... If your user base is localized, you won't see too much difference working with S3 or CloudFront (but you have to choose the right location for your S3 bucket: US, EU, APAC).

If your user base is spread, CloudFront should be a better option. Another difference is that CloudFront allows you to set different domain aliases for your CloudFront distribution: You can have for example d1.mystatics. Com, d2.mystatics.Com and d3.mystatics.

Com pointing to the same CloudFront distribution, allowing parallel downloads.(Google).

Thanks, great answer. – Kamo Jul 26 '10 at 7:27.

Another major difference is that cloudfront allows you to mirror the site on your server. Cloudfront then caches the files such as images, mp3 or video using it's content delivery network. This saves you having to duplicate your assets as you would when you use Amazon S3.

However after a file expires, Cloudfront will fetch it again from your live site (at cost). So cloud front is best for frequently accessed files, and less so for infrequently accessed ones. One way to set the file expiry for apache is in .htaccess.

For example Header set Cache-Control "max-age=648000, private.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.