[AWS] CloudFront, Route 53, Direct Connect: Understanding Networking Roles through Transportation Metaphors

*This page contains promotional content

Introduction: Simply creating a VPC leaves it as an "isolated island"

Even if you build a great server in a VPC, it's meaningless if users can't reach it.
AWS provides a suite of networking services to guide users to your server "fast, safely, and without getting lost."

In this article, I will organize these services by comparing them to a "transportation system." After reading this, you won't be confused by service names anymore.

1. Route 53 (DNS): The Internet's "GPS Navigation"

Everything starts here.

• Role: Translating URLs (www.example.com) into IP addresses (addresses).
• Features: It's more than just a phone book.
  • Health Check Function: It's a smart navigator that says, "This server is down, so I'll guide you to a different one."
  • You can also purchase domains directly from AWS.

2. Delivery and Optimization: Delivering Users at "Lightning Speed"

This is the "acceleration" area often searched for in SEO. Let's learn the differences.

• CloudFront (CDN):

  • Example: "The nearest convenience store (Distribution Center)".
  • How it works: It copies frequently used data (images or videos) and places them in Edge Locations (convenience stores) around the world. Users don't have to travel all the way to the headquarters (server).
  • Use cases: Speeding up website display, video streaming.

• Global Accelerator:

  • Analogy: "A paid private highway".
  • How it works: While standard internet lines (public roads) get congested, this uses AWS's dedicated lines to head straight to the server.
  • Use cases: Accelerating communications that cannot be cached, such as gaming or finance.

3. Connectivity (Hybrid): Connecting Your Company to AWS

Used when you want to "use AWS securely from the company office."

• Site-to-Site VPN:
  • Example: An "encrypted tunnel" created over the internet.
  • Features: Cheap and fast. However, since it passes through public roads (the internet), it might experience occasional latency.
• Direct Connect (DX):
  • Example: Bringing a "physical dedicated line" into the office.
  • Features: Expensive and takes time for construction. But it's a dedicated track that will never be obstructed. Large corporations choose this.

4. ELB (Load Balancing): The "Traffic Controller" at the Entrance

It works right in front of the servers.

• Role: Distributing a large volume of traffic evenly across multiple EC2 instances.
• Types: ALB: For websites (routing based on content).
  NLB: For ultra-high speed and massive traffic (routing based on packets).

Summary: The Ironclad Rules for Choosing Networking Services

• For name resolution: Route 53
• For speeding up static content (images/videos): CloudFront
• For speeding up dynamic communications (games, etc.): Global Accelerator
• For easy site-to-site connection: VPN; for quality-focused connection: Direct Connect
  

As long as you use the right service in the right place, AWS networking is incredibly powerful.

Afterword

Because networking is "invisible," it's best understood through diagrams. Setting up VPNs or Direct Connect is an area that's difficult to try out casually with a personal account (since Direct Connect requires physical construction...). To avoid embarrassment in professional practice, I read these "Infrastructure Design Pattern" books and simulated the scenarios in my mind. I highly recommend them as they offer a wealth of architectural patterns.

"AWS Certified Advanced Networking - Specialty"
https://amzn.to/3MQn5Gx
"AWS Guide to Construction and Operation by Pattern"
https://amzn.to/4sez0OB