For static files, store the definitive versions of your files in one or many origin servers. These can be Amazon S3 buckets. For your dynamically generated content that’s personalized or custom-made, you’ll be able to use Amazon EC2 – or the other net server – because of the origin server. These AWS CloudFront Private Pricing Partners can help you to store or generate your content which data will distribute through Amazon CloudFront.
Register your origin servers with Amazon CloudFront through an easy API decision. This decision can come from a CloudFront.net name that you will use to distribute content from your origin servers via the Amazon CloudFront service. For example, you’ll be able to register the Amazon S3 bucket because the origin for all of your static content Associate in an Amazon EC2 instance for all of your dynamic content. Then, exploiting the API or the AWS Management Console, you’ll be able to produce Associate in Nursing Amazon CloudFront distribution that may come in a form because of the distribution name.
Include the AWS CloudFront Private Pricing Partner you just contact in your web application, media player, or website. Every request created exploitation the cloudfront.net name is routed to the sting location best suited to deliver the content with the best performance. The sting location can decide to serve the request with an area copy of the file. If an area copy isn’t accessible, Amazon CloudFront can get a replica from the origin. This copy is then accessible at that edge location for future requests.