AWS CloudFront

 Amazon CloudFront is a global web service that allows you to securely deliver content to your users with low latency and high availability. It does so by further delivering content safely.  This service helps to built high performance and security in your application. CloudFront works for both static and dynamic content such as .html, .css  etc. CloudFront delivers the content worldwide with best possible performance. It also helps in speedy distribution of content.    

How is this done?

Cloudfront uses edge locations to serve the user’s request.  

  • Origin server: It can be an S3 bucket, EC2 instance, or your own HTTP server where files or objects are stored. Furthermore, origins can be ELB (Elastic load balancer) or Route 53.
  • Edge location: This is where the contents are cached. The data expires after a certain amount of time. After the data expires, the latest version of data is accessed from the origin server. Amazon regularly adds edge locations.
  • Regional Edge cache: Regional edge cache has a larger cache as compared to edge location. It can make data accessible even faster when users are requesting less popular content. Since the data stored at the edge location expires in a definite amount of time ( 24 hours expiration period by default, you can change the expiration period by setting cache-control header), edge locations can fetch data from regional edge cache rather than accessing it from the origin server thus retrieving the data even faster.  

Edge location; Regional Edge cache and origin server

  1. The user requests the data from the nearest edge location.
  2. If the cached data is present at the edge location then the request is served from the edge location.
  3. If the data is not present at the edge location then it is fetched from the regional edge cache (regional cache has a larger cache width).
  4. In the absence of a regional edge cache, the data is fetched directly from the origin server after expiration. But using regional edge cache provides low latency.

To know from which origin server the CloudFront needs to fetch the files, it uses CloudFront distribution.  

Use cases:

Following are some of the use cases of Cloudfront:

  • When you have users distributed worldwide, using cloudfront is a good practice to reduce latency.
  • Cloudfront can help your users access the popular content of your website with low latency or in less amount of time.
  • Cloudfront can be used to serve live and on-demand video streaming.
  • Acceleration of static content delivery
  • Encrypts fields via system processing

Benefits:

Following are the benefits of using cloudfront:

  • Cloudfront can be used to deliver both static as well as dynamic content with faster performance.
  • Protection against DDOS attacks.
  • Protection against layer 3 and 4 network attacks.
  • Cloudfront can be integrated with AWS WAF for application-layer protection.
  • You can restrict your content access.
  • CloudFront is cost effective as it works on pay-as-you-go pricing model.
  • Provides an option to encrypt your data with a free custom TLS certificate from ACM (Amazon Certificate manager) or using your own imported certificate.

Comments

Post a Comment

Popular posts from this blog

Terraform

Image
  Terraform is an infrastructure as code tool that lets you build, change, and version cloud and on-prem resources safely and efficiently. HashiCorp Terraform is an infrastructure as code tool that lets you define both cloud and on-prem resources in human-readable configuration files that you can version, reuse, and share. You can then use a consistent workflow to provision and manage all of your infrastructure throughout its lifecycle. Terraform can manage low-level components like compute, storage, and networking resources, as well as high-level components like DNS entries and SaaS features. How does Terraform work? Terraform creates and manages resources on cloud platforms and other services through their application programming interfaces (APIs). Providers enable Terraform to work with virtually any platform or service with an accessible API. HashiCorp and the Terraform community have already written  thousands of providers  to manage many different types of resources and services.
Read more

Scrum Master Interview help - Bootcamp

Understanding the MoSCoW prioritization | How to implement it into your project Projects, irrespective of their size or complexity, often juggle numerous tasks and requirements. In such a scenario,  MoSCoW prioritization  becomes essential to ensure the successful completion of the project.  Besides, it is also a very effective way to manage project priorities. With a straightforward and adaptable approach, the MoSCoW method helps manage stakeholder expectations and improve project outcomes. What is the MoSCoW prioritization technique?  The MoSCoW method is a prioritization matrix widely used in project management and software development. The term MoSCoW is an acronym that stands for  Must have ,  Should have ,  Could have , and  Won’t have , each denoting a level of priority. Here is the breakdown of the MoSCoW method:  Must have:  These are critical requirements that the project cannot be completed without them. If these are not fulfilled, the project is con
Read more

Kubernetes

  Using containers to host applications and other processes has gone mainstream. As more and more workload is moved into containers, management systems are needed to handle the demands of containerized applications at scale. One of the most popular options for managing  container-based workload is Kubernetes . Kubernetes combines container management automation with an extensible API to create a cloud-native application management powerhouse. At its core, Kubernetes manages the placement of pods, which can consist of one or more containers, on a Kubernetes cluster node. Additionally, if one of these pods crashes, Kubernetes can create a new instance of it. If a cluster node is removed, Kubernetes can move any affected workload to a different node in the cluster. On top of that, Kubernetes pods can be scaled to provide more or less throughput to meet scale demands and these scale operations can be triggered manually or automatically using Kuberentes horizontal pod auto-scaling. Finally,
Read more