You have a collection of assets stored in an S3 bucket.
You want to enable users across the world to access these assets with the least latency.
The users must also access the distribution via your company domain name.
How can you achieve this? Choose 2 answers from the options given below.
Click on the arrows to vote for the correct answer
A. B. C. D.Answer - A and C.
This is also given in the AWS Documentation.
Routing Traffic to an Amazon CloudFront Web Distribution by Using Your Domain Name.
If you want to speed up the delivery of your web content, you can use Amazon CloudFront, the AWS content delivery network (CDN)
CloudFront can deliver your entire website-including dynamic, static, streaming, and interactive content-by using a global network of edge locations.
Requests for your content are automatically routed to the edge location that gives your users the lowest latency.
Note
You can route traffic to a CloudFront distribution only for public hosted zones.
To use CloudFront to distribute your content, you create a web distribution and specify settings such as the Amazon S3 bucket or HTTP server that you want CloudFront to get your content from, whether you want only selected users to have access to your content, and whether you want to require users to use HTTPS.
When you create a web distribution, CloudFront assigns a domain name to the distribution, such as d111111abcdef8.cloudfront.net.
You can use this domain name in the URLs for your content, for example:
http://d111111abcdef8.cloudfront.net/logo.jpgAlternatively, you might prefer to use your own domain name in URLs, for example:
http://example.com/logo.jpgIf you want to use your own domain name, use Amazon Route 53 to create an alias record that points to your CloudFront distribution.
An alias record is a Route 53 extension to DNS.
It's similar to a CNAME record, but you can create an alias record both for the root domain, such as example.com, and for subdomains, such as www.example.com.
(You can create CNAME records only for subdomains.) When Route 53 receives a DNS query that matches the name and type of an alias record, Route 53 responds with the domain name that is associated with your distribution.
Option B is incorrect since you can't use S3 behind the Application Load balancer.
Option D is incorrect because you need to define an ALIAS record.
For more information on routing to Cloudfront, one can visit the below URL.
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-to-cloudfront-distribution.htmlTo enable users across the world to access assets stored in an S3 bucket with the least latency, we can use Amazon CloudFront and Amazon Route 53.
Amazon CloudFront is a content delivery network (CDN) that distributes data from S3 or other origin servers to edge locations around the world. When a user requests content from CloudFront, the request is routed to the nearest edge location, which then serves the content. This reduces the latency and improves the user experience.
Amazon Route 53 is a domain name system (DNS) service that routes users to internet resources such as web servers and load balancers. Route 53 can route users to CloudFront distributions, S3 buckets, or application load balancers.
To achieve the objective of allowing users to access the assets with the least latency and via your company domain name, we can follow the below steps:
Create a CloudFront distribution: We can create a web-based distribution in CloudFront and configure it to use our S3 bucket as the origin server. This will enable CloudFront to cache the content of our S3 bucket and serve it from its edge locations around the world.
Configure Route 53: We can create a resource record in a hosted zone and create an ALIAS record to point to the CloudFront distribution. An ALIAS record provides a Route 53-specific extension to DNS functionality that lets you map a domain name to an AWS resource.
In summary, the correct answers are A and C. By using Amazon CloudFront and Amazon Route 53, we can distribute the content from S3 across multiple edge locations and route users to the nearest edge location via our company domain name, resulting in faster content delivery and a better user experience.