CloudIntermediate10 min readJul 19, 2026By Tech-ikigai Instructors
π§βπ³ A beginner's tour through AWS
You built tech-ikigai.com on EC2... now what?
You hosted your website on a single AWS server called EC2. A friend types your address into a browser. What actually happens between their click and your page appearing? Let's follow that journey like a delivery order to a restaurant inside a giant mall called AWS.
π https://tech-ikigai.com
π’ The AWS "Mall Map"
AWS is really just boxes inside boxes. Here's where your little restaurant (EC2) actually sits.
This is also the exact order beginners should check things when a site "isn't loading."
Success pathCommon beginner problem
1
You hit Enter
"Have I ordered from here before?"
π§ Just like checking your phone for a saved contact before calling β the browser first checks its own memory (cache) for tech-ikigai.com before asking anyone else.
Browser checks its own cache, then the computer's DNS cache.
Not found? Time to ask Amazon's phonebook: Route 53.
π You created a listing in Amazon's own address book (a "Hosted Zone" in Route 53) that says: "tech-ikigai.com lives at this exact IP address." Anyone asking gets that answer.
An A record in Route 53 points your domain to your EC2 instance's public (or Elastic) IP address.
This answer gets cached for a while so the next visitor's lookup is instant.
π Try it yourself
dig tech-ikigai.comnslookup tech-ikigai.com
Look for the "ANSWER" section β that's the IP address Route 53 handed back.
3
Crossing the internet
The delivery truck's long drive
π Now that the browser has the address, it hands the request to a delivery truck that hops through many toll booths (routers) β your Wi-Fi, your ISP, and the wider internet β heading straight for the AWS mall.
Each hop is a router forwarding the packet a little closer to AWS's network.
Usually takes just a few milliseconds, even across countries.
Each numbered line is one router hop on the way to AWS.
4
Internet Gateway β the front door
Arriving at the AWS mall's main entrance
πͺ AWS's whole "mall" (your VPC β Virtual Private Cloud) has exactly one official front door for internet traffic: the Internet Gateway (IGW). No IGW attached, no visitors get in at all.
The IGW is attached to your VPC and allows traffic in and out from the public internet.
Without it, your EC2 instance would be completely unreachable from outside, no matter what else is configured.
π Check it in AWS Console
VPC β Internet Gateways β State: attached
5
Route Table β the hallway directory
Finding the right hallway
πΊοΈ Once inside the mall, a directory board (Route Table) tells the delivery person exactly which hallway (subnet) leads to your shop.
The route table for your public subnet has an entry saying "for internet traffic (0.0.0.0/0), go through the IGW."
This is what makes a subnet "public" in the first place β not the name, the route!
π Right before anyone reaches your actual shop, a bouncer (Security Group) checks a guest list: "Are you allowed in on port 80 (http) or 443 (https)?" There's also a simpler outer fence check first (Network ACL) at the hallway's entrance β but the Security Group is the one guarding your door specifically.
Security Groups are stateful β if a request is let in, the reply is automatically allowed back out, no extra check needed.
This is the #1 place beginners forget to open a port!
π³ The order finally reaches your restaurant's kitchen β the EC2 instance. A web server program (like Nginx or Apache) reads the order (the HTTP request) and starts preparing your webpage.
The web server matches the request to your website's files and builds an HTTP response.
If the server software isn't installed or isn't running, this is where a "502 Bad Gateway" or blank page comes from.
π Try it yourself (after SSH into the instance)
sudo systemctl status nginxcurl -I http://localhost
8
The way back
The food heads back out
π΅ The finished webpage is packed up and sent right back out the same path β hallway, front door, across the internet β straight to the browser that ordered it. Because the Security Group remembered the visitor, this trip doesn't need a fresh guest-list check.
Route Table β Internet Gateway β across the internet β your ISP β your router β your PC.
If the page is big, it arrives as many packets, numbered and reassembled in order.
9
Ta-da!
Your browser paints the page
π All the packets are reassembled into HTML, CSS, and images. Your browser reads that and draws tech-ikigai.com right on the screen β usually in well under a second, even though it just crossed the whole internet and back!
π Try it yourself
curl -v https://tech-ikigai.com
The -v flag shows the DNS lookup, TLS handshake, and the final HTML β the whole journey in one command.
π¦ What's actually inside that packet?
Peeking inside the "envelope" your browser sends, wrapped layer by layer.