SAA-C03 ยท High-performing networks and edge
Amazon CloudFront
Edge caching of static and dynamic content, origins (S3 with origin access control, ALB, custom), cache behaviors and TTLs, and signed URLs.
Key points
- CloudFront: AWS CDN; edge locations cache near viewers, cutting latency and origin load.
- Origins: S3, ALB, any HTTP server; cache behaviors map paths (/api/*) to an origin.
- TTL: Minimum, Default, Maximum plus Cache-Control/Expires; no cache policy = 24 hours.
- OAC keeps S3 private (replaced OAI, supports SSE-KMS); not for S3 website endpoints (custom origins).
- Signed URLs: single files; signed cookies: many files, same URLs.
Source: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/Expiration.html
Practice questions
Which CloudFront feature is recommended for letting only your distribution read objects from a private S3 bucket?
- Origin access identity (OAI)
- Origin access control (OAC)
- Signed URLs for each object
- An S3 public access point
Show answer
Answer: B. Origin access control (OAC)
Origin access control (OAC) signs CloudFront's requests to S3, and the bucket policy allows the cloudfront.amazonaws.com principal only for that distribution. OAI is the legacy mechanism and lacks features such as SSE-KMS support; signed URLs control viewers, not CloudFront's access to the bucket.
Which of the following can be configured as a CloudFront origin?
- An Amazon S3 bucket
- An Application Load Balancer
- An Amazon EBS volume
- An on-premises HTTP web server
- A DynamoDB table
Show answer
Answer: A. An Amazon S3 bucket, B. An Application Load Balancer, D. An on-premises HTTP web server
CloudFront pulls from an S3 bucket, an Application Load Balancer, or any custom HTTP server such as an EC2 web server or an on-premises site. An EBS volume is block storage attached to an instance, and a DynamoDB table has no HTTP endpoint that CloudFront can cache from directly.
An S3 bucket configured as a static website endpoint can be protected with CloudFront origin access control, just like a regular bucket origin.
Show answer
Answer: False
False. A website endpoint must be added to CloudFront as a custom origin, and custom origins cannot use OAC (or OAI). To use OAC, point CloudFront at the regular bucket endpoint instead.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
