Task Statement 4.4: Design cost-optimized network architectures.

📘AWS Certified Solutions Architect – (SAA-C03)

The main AWS service for this is Amazon CloudFront, which is the global CDN service used to deliver content faster and reduce load on origin servers.

1. What is a CDN (Simple Understanding)

A Content Delivery Network (CDN) is a system that:

Stores copies of data in multiple global locations
Delivers content from the nearest location to the user
Reduces load on the original server (origin)

In AWS, CDN is implemented using Amazon CloudFront with edge locations worldwide.

2. What is Edge Caching?

Edge caching means:

Storing content (files, images, APIs, videos) at AWS edge locations
So users do NOT always request data from the origin (like S3 or EC2)
Instead, they get cached data from nearby edge servers

Example in AWS terms:

Origin = Amazon Web Services S3 bucket or ALB
Edge location = CloudFront cache server near the user
First request goes to origin
Next requests are served from cache

3. Why CDNs and Edge Caching Are Important (Exam Focus)

You use CDNs when you want to optimize:

3.1 Performance (Latency Reduction)

Users get content from nearby edge location
Reduces network distance and latency
Important for global applications

3.2 Cost Optimization

CDNs reduce cost in several ways:

(a) Reduce data transfer from origin

Less traffic hits S3/EC2/ALB
Saves origin bandwidth cost

(b) Reduce compute load

Fewer requests to backend servers
Less scaling required

(c) Reduce cross-region traffic

Avoid expensive inter-region data transfer

3.3 Scalability

CDN absorbs traffic spikes
Edge caches handle many requests without hitting origin

3.4 Security

CDNs can also:

Protect origin using caching layer
Work with AWS Shield and AWS WAF
Hide origin endpoints

4. Strategic Decision: When to Use CDN (Very Important for Exam)

You should choose CDN when:

4.1 Global Users

Use CDN if:

Users are spread across countries
Need consistent fast response worldwide

Example:

Static website accessed from Asia, Europe, US

4.2 Static Content Delivery

Best for:

Images
Videos
CSS/JS files
Software downloads

These files:

Rarely change
Cache well

4.3 High Traffic Websites

Use CDN when:

Too many requests overload origin
You want to reduce backend scaling cost

4.4 API Acceleration (Carefully)

CDNs can cache:

GET API responses
Public or semi-static API data

Not good for:

Highly dynamic personalized data (unless carefully configured)

4.5 Media Streaming

Use CDN for:

Video streaming
Large file downloads

5. Key Edge Caching Concepts (Exam Must-Know)

5.1 Cache Hit vs Cache Miss

Cache Hit

Data found at edge
Fast response
No origin request
Lowest cost

Cache Miss

Data not in edge
Request goes to origin
Higher latency + cost

5.2 TTL (Time to Live)

Defines how long content stays in cache
Higher TTL = fewer origin requests = lower cost
Lower TTL = more freshness but more cost

5.3 Cache-Control Headers

Controlled by origin server:

Cache-Control: max-age=...
no-cache (forces validation)
no-store (disables caching)

5.4 Invalidation

Used when content changes before TTL expires
Forces CloudFront to remove cached content
Can increase cost if used frequently

6. Origin Types in AWS CDN Architecture

CDN can use multiple origins:

Amazon S3 (static content)
Application Load Balancer (dynamic apps)
EC2 instances
API Gateway

Most common exam pattern:

Static site → S3 + CloudFront
Web app → ALB + CloudFront

7. Advanced Strategic Features (Exam-Level Understanding)

7.1 Origin Shield

Extra caching layer between edge and origin
Reduces origin load further
Improves cache hit ratio

7.2 Compression

CloudFront compresses files (gzip, Brotli)
Reduces bandwidth cost

7.3 Signed URLs / Cookies

Used when:

Content is private
You want controlled access via CDN

7.4 Geo Restrictions

Restrict content by country
Useful for licensing or compliance

8. CDN vs Direct Access (Exam Decision Point)

Without CDN:

Every request hits origin
Higher latency
Higher cost
Higher server load

With CDN (CloudFront):

Most requests served from edge
Lower latency
Lower cost
Better scalability

9. Exam Scenarios You Must Recognize

Scenario 1: High global traffic static website

✔ Use CloudFront + S3

Scenario 2: Reduce EC2 load for frequently accessed images

✔ Use CloudFront caching

Scenario 3: Video streaming platform

✔ CloudFront for large file distribution

Scenario 4: Reduce inter-region data transfer cost

✔ Use edge caching instead of cross-region requests

Scenario 5: Highly dynamic personalized API

❌ Do NOT cache aggressively
✔ Maybe partial CDN usage with careful TTL rules

10. Key Exam Keywords (Very Important)

If you see these words, think CDN / Edge caching:

“global users”
“low latency worldwide”
“reduce origin load”
“static content delivery”
“reduce data transfer cost”
“cache frequently accessed content”
“edge locations”
“high traffic spikes”

11. Final Summary (Exam Ready)

You use CDN and edge caching (via Amazon CloudFront) to:

Improve global performance by serving content from nearby locations
Reduce origin server load
Reduce AWS data transfer and compute costs
Improve scalability during traffic spikes
Secure and control content delivery

The key exam idea is:

“If content can be cached at the edge, do not repeatedly fetch it from the origin — this reduces cost and improves performance.”