Published on Jan 30,2018
536 Views
Email Post

To get started with Amazon Cloud front, it is important to know the pros and cons of Web Servers. The advantage of Web Server is the ability to store content in a static level, whereas the disadvantage is that place, which hosts the server will be faster than those in other locations.

Content Delivery Network

The feature in Cloud front called the ‘Content Delivery Network (CDN) or Age Location’ caches the static content, which can be anything varying from a basic html to a video file.

Typically, when a query is made, it would be returning from CDN rather than the main server. The advantage being here is the lower latency, higher throughput and decrease in load time on the web server.

Through CDN, it can publicly edge cache readable static objects, where the pay-as-you-go feature with no commitments is provided. Along with that, there are 51 Edge locations across the world.

For example:

If an object is uploaded in Amazon S3, then the url will be:

S3.amazonaws.com/bucketname/objectname.

In case, one has to use the Cloud Front, the Bucket can be selected and a distribution must be created. In this way, the Cloudfront specific Url/DNS can be acquired.

It’s important to know, if in a website, which has files, be it a logo file, or image file, the URL must be a cloudfront URL, rather than an S3 URL. So, whenever a page is loaded, it would find the URL from cloudfront. The same concept applies to other types of files as well. In this case, it will download object from S3 and store inside caching server. Initially it shall download, but after that it won’t go to S3.

Also, there are options to check the version of the object. When there is a newer version available, it will download, otherwise it will return from age location. Along with that, there are options to set up time-out for each object. In this case, it is 24 hours, after which it will go back to the age location and get a new object.

User Question 1

Will it increase the cost as it stored in cloudfront, as well as the serving user?

Yes, based on its service on the performance part, since performance is more important than cost. In this scenario, if the image is larger than 1 MB, when a request is made, it will load from S3, and there are chances that the performance can get affected. But in age location, the cost is cheap and the performance cost will decrease.

User Question 2

Can we configure which part of a website needs to be cached or can we cache everything by default?

Here, once we cache, a distribution from bucket is created. In this case, it will never use cloud front or it will come directly from the origin. So whatever URL is given to the object in cloudfront, it will follow the cloud front law and cache the object. Thus, it is completely in user’s control on what to and what not to cache.

The various Cloudfront highlights are:

  • Its fast, simple & reliable
  • The content is delivered using http or https protocol access policy through private content feature
  • Streaming is done through real-time messaging protocol
  • Elasticity of service

While working with Cloud Front, a distribution is created, based on where the origin is (S3 or Public site). It is distributed in two ways, which means it can be downloaded (html/css image files) or streamed.

It works in the user domain as well.

For example, if it gives a domain name, xyz.cloudfront.amazonaws.net and if the user wants to use his/her own domain name, it is possible with a default expiry time of 24 hours.

Here are the steps to be followed:

Services-> Database -> CloudFront -> Distribution

In this case, the distribution is already created.

In order to create a distribution, the following criteria must be fulfilled.

  1. Create Distribution [Choose between Web (Download distribution) or RTMP (Streaming distribution)].
  2. Origin Domain Name (based on where the object is stored)
  3. Restricting Bucket Access
  4. Viewer Protocol Policy(HTTP or HTTPS)
  5. HTTP Methods & Forward Headers(For caching performance enhancement)
  6. Object caching & Forward Query Strings
  7. Smooth Streaming
  8. Restrict viewer access (in case a private url has to be created for each cloudfront distribution)
  9. Pricing (based on 3 options that can be chosen by location)

Here, the distribution, which will have details along with the domain name (mapped to a bucket) is created. The bucket has 2 objects which can be accessed with the URL.

Here HTML & Object are served from Cloud front.

 Got a question for us? Mention them in the comments section and we will get back to you.

Related Posts:

6 AWS Cloud Cases which are Revolutionizing Business

Learn AWS with Cloud Computing

About Author
edureka
Published on Jan 30,2018

Share on

Browse Categories

Comments
0 Comments