A company is hosting its static website in an Amazon S3 bucket, which is the origin for Amazon CloudFront. The company has users in the United States, Canada, and Europe and wants to reduce costs. What should a solutions architect recommend?
A.
Adjust the CloudFront caching time to live (TTL) from the default to a longer timeframe.
B.
Implement CloudFront events with Lambda@Edge to run the website's data processing.
C.
Modify the CloudFront price class to include only the locations of the countries that are served.
D.
Implement a CloudFront Secure Sockets Layer (SSL) certificate to push security closer to the locations of the countries that are served.
A. This could be an option, since static content won't change that much.
B. It's a static website, there is no processing.
C. Sounds about right. https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/PriceClass.html
D. What does an SSL have to do with reducing costs?
Yes agreed, the answer is definitely C. As per the link below “ A third price class includes only the least expensive regions (the United States, Canada, and Europe regions).” https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/PriceClass.html
https://aws.amazon.com/cloudfront/pricing/:
"Price classes provide you an option to lower the prices you pay to deliver content out of Amazon CloudFront"
".Price Classes let you reduce your delivery prices by excluding Amazon CloudFront’s more expensive edge locations from your Amazon CloudFront distribution."
C is the answer
Answer is C
CloudFront edge locations are grouped into geographic regions, and we've grouped regions into price classes. The default price class includes all regions. Another price class includes most regions (the United States; Canada; Europe; Hong Kong, Philippines, South Korea, Taiwan, and Singapore; Japan; India; South Africa; and Middle East regions) but excludes the most expensive regions. A third price class includes only the least expensive regions (the United States, Canada, and Europe regions).
https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/PriceClass.html
Folks a question to you guys who are going for C. Amazon Cloud Front charges based on region not by price class. And some regions are costly like India where as US / Mexico & Canada is the cheapest. (https://aws.amazon.com/cloudfront/pricing/) Now in this case the customer base is already within the cheapest priced regions so moving to the cheapst price class - will it serve any cost optimisation ?
Ofcourse A seems to be not the answer as CF to S3 as origin data transfer charge seems to free (https://aws.amazon.com/cloudfront/pricing/)
While C is probably the correct answer and what you say is also true, increasing the TTL will also reduce the amount of requests that will reach the s3 origin thus reducing the s3 outbound traffic costs.
That’s why A isn’t a completely off answer as well.
C is correct . CloudFront has edge locations all over the world. Our cost for each edge location varies and, as a result, the price that we charge you varies depending on the edge location from which CloudFront serves your requests.
CloudFront edge locations are grouped into geographic regions, and we've grouped regions into price classes. The default price class includes all regions. Another price class includes most regions (the United States; Canada; Europe; Hong Kong, Philippines, South Korea, Taiwan, and Singapore; Japan; India; South Africa; and Middle East regions) but excludes the most expensive regions. A third price class includes only the least expensive regions (the United States, Canada, and Europe regions).
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
sctmp
Highly Voted 3 years, 8 months agoaguy9
3 years, 7 months agojy00271070
Highly Voted 3 years, 8 months agosamuel1999
Most Recent 3 years, 6 months agosyu31svc
3 years, 7 months agoYogi
3 years, 7 months agoDoktaDee
3 years, 7 months agoSam82
3 years, 7 months agoalgreat
3 years, 7 months agoAtanu_M
3 years, 7 months agoqurren
3 years, 7 months agoTwinkie
3 years, 7 months agokimalto452
3 years, 7 months agoanpt
3 years, 7 months agosuku555
3 years, 7 months agomlammy76
3 years, 8 months agospring21
3 years, 8 months agomassyg
3 years, 8 months agojulian_58
3 years, 8 months agotheCreatorSD
3 years, 7 months ago