CloudFront

Question 1

Difference in location for CF Functions and Lambda@Edge

Answer 1

CF Functions reside at the 218+ Edge Locations

Lambda@Edge exists at the 13 Regional Edge Locations – closer to the origin

Question 2

How to configure CF Standard (Access) Logs? Where and how often are they delivered?

Answer 2

Configure on a distribution, send to S3. Sent multiple times an hour, but can delay up to 24 hours

Question 3

What are CF Real-time logs, and how to configure?

Answer 3

Within-seconds logs. Delivered to KDS. From there, you can build your own consumer, or use KDS —> KDF —> S3

Question 4

What is the point of CF Origin Groups?

Answer 4

Failover. With origins in an origin group (primary / secondary), you can configure failover

Question 5

I can use URL paths in my CF distribution to route to many different origins. How does Lambda@Edge improve upon this?

Answer 5

By running code in response to requests. Can make decisions on more factors – headers, cookies, query strings, viewer country, etc.

Question 6

What is “S3 Zone Apex Support,” and why is it relevant to CloudFront?

Answer 6

This refers to the power of an Alias record to point from a root domain to another AWS resource (in this case, S3) So this allows you to point 222323.cloudfront.net –> examplebucket.s3.amazonaws.com, as for static website hosting