DEV Community

Anupa Supul
Anupa Supul

Posted on

How Does AWS Know Which Website I'm Trying to Visit? Understanding Amazon Route 53

#aws #cloudcomputing #amazon #route

When I first started learning web development, opening a website felt almost magical.

I would type something like:

www.amazon.com
Enter fullscreen mode Exit fullscreen mode

Press Enter.

A few seconds later, the website appeared.

I never stopped to think about what actually happened.

How did my computer know where Amazon's servers were?

How did it find the correct server among millions connected to the internet?

And why don't we type an IP address like:

54.239.28.85
Enter fullscreen mode Exit fullscreen mode

instead of simply typing:

amazon.com
Enter fullscreen mode Exit fullscreen mode

Those questions eventually led me to one of the first networking services in AWS:

Amazon Route 53

The Question That Made Me Curious

Imagine I build my own MERN application.

I deploy it on an EC2 instance.

AWS gives me a public IP address like:

18.142.120.54
Enter fullscreen mode Exit fullscreen mode

Technically, people can visit my application using that IP.

But let's be honest...

Nobody wants to remember numbers like that.

It's much easier to visit:

myportfolio.com
Enter fullscreen mode Exit fullscreen mode

or

myapp.com
Enter fullscreen mode Exit fullscreen mode

That made me wonder:

How does my computer know that "myapp.com" actually means "18.142.120.54"?

The Phone Contact Analogy

This example made everything click for me.

Imagine your best friend has this phone number.

+94 71 123 4567
Enter fullscreen mode Exit fullscreen mode

Do you memorize the number?

Probably not.

Instead, you save it as:

John
Enter fullscreen mode Exit fullscreen mode

Now whenever you want to call him, you simply tap:

John
Enter fullscreen mode Exit fullscreen mode

Your phone automatically finds the correct phone number.

You don't need to remember it.

The internet works almost the same way.

Instead of remembering:

18.142.120.54
Enter fullscreen mode Exit fullscreen mode

we simply remember:

mywebsite.com
Enter fullscreen mode Exit fullscreen mode

Something translates that easy-to-read name into the server's IP address.

That "something" is called DNS (Domain Name System).

What Is Amazon Route 53?

Amazon Route 53 is AWS's managed DNS service.

Its job is simple:

Convert human-friendly domain names into IP addresses that computers understand.

Instead of this:

18.142.120.54
Enter fullscreen mode Exit fullscreen mode

We simply type:

mywebsite.com
Enter fullscreen mode Exit fullscreen mode

Route 53 performs the translation and sends us to the correct server.

What Actually Happens?

Let's say I open:

www.myportfolio.com
Enter fullscreen mode Exit fullscreen mode

Here's what happens behind the scenes.

flowchart LR

A[User Types myportfolio.com]

-->B[Browser]

-->C[Amazon Route53 DNS Lookup]

-->D[Returns IP Address]

-->E[EC2 Server]

-->F[Website Loads]
Enter fullscreen mode Exit fullscreen mode

The entire process usually takes only milliseconds.

A Real AWS Example

Suppose I host my MERN application on an EC2 instance in Singapore.

Its public IP address is:

18.xxx.xxx.xxx
Enter fullscreen mode Exit fullscreen mode

Without Route 53, users would have to visit:

18.xxx.xxx.xxx
Enter fullscreen mode Exit fullscreen mode

With Route 53:

flowchart LR

A[myportfolio.com]

-->B[Amazon Route53]

-->C[18.xxx.xxx.xxx]

-->D[EC2 Instance]
Enter fullscreen mode Exit fullscreen mode

Much easier.

Why Is It Called Route 53?

One thing that caught my attention was the number 53.

It's actually named after Port 53, the standard network port used for DNS communication.

A small detail, but one I found interesting.

Route 53 Does More Than DNS

Initially, I thought Route 53 only converted domain names into IP addresses.

But it can also:

  • Route traffic globally
  • Perform Health Checks
  • Fail over to healthy resources
  • Route traffic intelligently
  • Improve application availability

Where Route 53 Fits in AWS

As I learned more AWS services, I realized Route 53 is usually the very first AWS service involved when someone opens a website.

flowchart LR

User

-->Route53

-->CloudFront

-->LoadBalancer

-->EC2

-->Database
Enter fullscreen mode Exit fullscreen mode

Every service has its own responsibility.

Route 53 simply helps users find the right destination.

Why Route 53 Matters

Without DNS:

Users must remember IP addresses.

With Route 53:

Easy-to-remember domain names

Highly available DNS

Faster routing

Health monitoring

Traffic routing policies

Works with almost every AWS service

What Changed My Perspective

Before learning AWS, I thought typing a website name directly connected me to the server.

Now I understand there's an important translation happening first.

Someone has to convert:

mywebsite.com
Enter fullscreen mode Exit fullscreen mode

into

18.xxx.xxx.xxx
Enter fullscreen mode Exit fullscreen mode

That's exactly what DNS does.

And in AWS, that job belongs to Amazon Route 53.

Final Thoughts

When I first heard the name Route 53, I had no idea what it actually did.

Now I think of it much more simply.

It's like the contact list on my phone.

I don't remember phone numbers.

I remember names.

Similarly, my browser doesn't magically know where a website lives.

Route 53 translates a human-friendly domain name into the server's actual address.

Sometimes the most important AWS services are the ones quietly working behind the scenes.

And Route 53 is definitely one of them.

Key Takeaways

  • Route 53 is AWS's managed DNS service.
  • It converts domain names into IP addresses.
  • It makes websites easier to access.
  • It supports health checks and intelligent routing.
  • It's usually the first AWS service involved when visiting a website.

*Thanks for reading! *

Top comments (0)