Edge locations and CloudFront overview in AWS - Mini Project: Build & Apply

Edge locations and CloudFront overview

📖 Scenario: You are setting up a simple AWS CloudFront distribution to deliver content faster to users worldwide by using edge locations.This project will guide you through creating the basic CloudFront distribution configuration step-by-step.

🎯 Goal: Build a CloudFront distribution configuration that uses a specified origin domain and enables caching at edge locations.

📋 What You'll Learn

Create a dictionary called origin_config with the origin domain name.

Add a configuration variable called default_cache_behavior with viewer protocol policy.

Create a dictionary called cloudfront_distribution combining origin and cache behavior.

Add the final DistributionConfig key with enabled status to complete the CloudFront distribution configuration.

💡 Why This Matters

🌍 Real World

CloudFront is used to speed up delivery of websites and content by caching it at edge locations close to users worldwide.

💼 Career

Understanding CloudFront configuration is essential for cloud engineers and architects working with AWS to optimize application performance and security.

1

Create the origin configuration

Create a dictionary called origin_config with the key DomainName set to example-bucket.s3.amazonaws.com.

AWS

# Create the origin_config dictionary with DomainName
# Your code here

Hint

Use a dictionary with the exact key 'DomainName' and value 'example-bucket.s3.amazonaws.com'.

2

Add default cache behavior configuration

Add a dictionary called default_cache_behavior with the key ViewerProtocolPolicy set to redirect-to-https.

AWS

origin_config = {
    'DomainName': 'example-bucket.s3.amazonaws.com'
}
# Add default_cache_behavior dictionary with ViewerProtocolPolicy
# Your code here

Hint

Create a dictionary named default_cache_behavior with the exact key and value.

3

Combine origin and cache behavior into distribution dictionary

Create a dictionary called cloudfront_distribution with keys Origins set to a list containing origin_config, and DefaultCacheBehavior set to default_cache_behavior.

AWS

origin_config = {
    'DomainName': 'example-bucket.s3.amazonaws.com'
}

default_cache_behavior = {
    'ViewerProtocolPolicy': 'redirect-to-https'
}
# Create cloudfront_distribution dictionary combining Origins and DefaultCacheBehavior
# Your code here

Hint

Use a dictionary with keys 'Origins' and 'DefaultCacheBehavior' referencing the previous dictionaries.

4

Add DistributionConfig enabled status

Add a key DistributionConfig to cloudfront_distribution with a nested dictionary containing Enabled set to True, and include the existing Origins and DefaultCacheBehavior inside it.

AWS

origin_config = {
    'DomainName': 'example-bucket.s3.amazonaws.com'
}

default_cache_behavior = {
    'ViewerProtocolPolicy': 'redirect-to-https'
}

cloudfront_distribution = {
    'Origins': [origin_config],
    'DefaultCacheBehavior': default_cache_behavior
}
# Add DistributionConfig key with Enabled set to true including Origins and DefaultCacheBehavior
# Your code here

Hint

Wrap the existing keys inside a new DistributionConfig dictionary and set Enabled to True.

Practice

1. What is the main purpose of AWS CloudFront edge locations?

easy

A. To deliver content closer to users for faster access

B. To store user data permanently

C. To run virtual machines

D. To manage AWS billing

Solution

1. Step 1: Understand edge locations role

   Edge locations are small data centers worldwide that cache content closer to users.

2. Step 2: Identify main benefit

   By caching content near users, edge locations reduce latency and speed up delivery.

3. Final Answer:

   To deliver content closer to users for faster access -> Option A

4. Quick Check:

   Edge locations = faster content delivery [OK]

Hint: Edge locations bring content physically closer to users [OK]

Common Mistakes:

• Thinking edge locations store permanent user data
• Confusing edge locations with main AWS regions
• Assuming edge locations run virtual machines

2. Which of the following is the correct way to specify an origin domain name in a CloudFront distribution configuration?

easy

A. origin-domain-name: example_com

B. originDomainName = example.com

C. origin_domain_name: "example.com"

D. originDomainName: 'example_com'

Solution

1. Step 1: Review CloudFront origin domain syntax

   CloudFront origin domain names are specified as strings with dots, e.g., "example.com".

2. Step 2: Check option formats

   origin_domain_name: "example.com" uses correct key and string format with quotes and dot notation.

3. Final Answer:

   origin_domain_name: "example.com" -> Option C

4. Quick Check:

   Correct syntax uses quotes and dots [OK]

Hint: Use quotes and dots for domain names in config [OK]

Common Mistakes:

• Using underscores instead of dots in domain names
• Missing quotes around domain strings
• Using incorrect key names or assignment symbols

3. Given a CloudFront distribution with an origin set to mybucket.s3.amazonaws.com and default cache behavior, what happens when a user requests a file not yet cached at the edge location?

medium

A. CloudFront serves a stale cached version from another edge location

B. CloudFront returns a 404 error immediately

C. CloudFront redirects the user to the origin URL

D. CloudFront fetches the file from the origin and caches it at the edge

Solution

1. Step 1: Understand CloudFront cache miss behavior

   If a requested file is not in the edge cache, CloudFront retrieves it from the origin.

2. Step 2: Confirm caching after retrieval

   After fetching, CloudFront caches the file at the edge location for future requests.

3. Final Answer:

   CloudFront fetches the file from the origin and caches it at the edge -> Option D

4. Quick Check:

   Cache miss triggers origin fetch and caching [OK]

Hint: Cache miss = fetch from origin + cache [OK]

Common Mistakes:

• Assuming CloudFront returns error on cache miss
• Thinking CloudFront redirects users to origin
• Believing stale cache is served from other edges

4. You configured a CloudFront distribution but users report slow content delivery. Which of the following is a likely misconfiguration causing this issue?

medium

A. Edge locations are disabled in the distribution settings

B. Origin domain name is set to a region far from users

C. Cache behavior is set to cache all content aggressively

D. SSL certificate is attached to the distribution

Solution

1. Step 1: Analyze origin location impact

   If the origin is far from users and cache misses occur, content fetch is slow.

2. Step 2: Check other options

   Edge locations cannot be disabled; caching aggressively improves speed; SSL does not slow delivery significantly.

3. Final Answer:

   Origin domain name is set to a region far from users -> Option B

4. Quick Check:

   Far origin = slower fetch on cache miss [OK]

Hint: Far origin causes slow fetch, not edge settings [OK]

Common Mistakes:

• Thinking edge locations can be disabled
• Believing SSL slows down delivery significantly
• Assuming aggressive caching causes slow delivery

5. You want to optimize a CloudFront distribution to serve a global audience with dynamic content that changes frequently. Which combination of settings best achieves low latency and fresh content delivery?

hard

A. Use multiple edge locations with short TTL cache settings and origin failover

B. Use a single origin with long TTL cache and disable edge caching

C. Use edge locations only in one continent and long TTL cache

D. Disable caching and serve all requests directly from origin

Solution

1. Step 1: Consider global audience needs

   Multiple edge locations reduce latency by serving users nearby worldwide.

2. Step 2: Handle dynamic content freshness

   Short TTL cache ensures content updates quickly; origin failover improves reliability.

3. Step 3: Evaluate other options

   Long TTL delays updates; single continent edges increase latency; disabling cache increases load and latency.

4. Final Answer:

   Use multiple edge locations with short TTL cache settings and origin failover -> Option A

5. Quick Check:

   Global edges + short cache + failover = best freshness & speed [OK]

Hint: Combine global edges with short cache for fresh, fast content [OK]

Common Mistakes:

• Using long TTL caches for dynamic content
• Limiting edge locations to one region
• Disabling caching causing high latency