Amazon Cloudfront

The book I read to research this post was Cloudfront Developers Guide which is an excellent book which I downloaded for free from kindle. There is quite a lot of information in this book along with some tutorials for AWS management console and even some scripts in various computer languages. If you had a web site on a web server in Seattle in Washington State & someone was looking at it on a desktop in Austin, Texas the signal might go threw 10 web servers to get there and each time it would slow the signal down and possibly degrade it. Cloudfront which either stores information which needs downloading or routes you threw to a server where the file can be downloaded keeps the number of servers it passes threw to a minimum. If you store the information on another it can either be a S3 or simple storage solution, or your own web server. If it's a RMTP file which is used by flash media server it must be a S3 server. The information can be HTTP, HTTPS, dynamic or live feed. Incidently you can have a web site hosted on a S3 server. The name they give to the file they call a cname and you can have upto 10 different ones which might come in handy if you sell information products. If you need a specific DNS name or web address for the file you may have to use the Route 53 service. If you use Cloudfront you can choose which continental server farm stores the information so that it is reasonably near your customers.