EC2 Is Not Just a Server: Understanding What Happens Behind the Scenes
When we launch an Amazon EC2 instance, it may look like we have simply created a server. But behind that EC2 instance, several AWS networking components are working together. In this article, I’ll explain how EC2, VPC, Subnets, Security Groups, Internet Gateway, and IP addresses work together using a simple real-world example. If you are new to AWS or DevOps, this article will help you understand what actually happens behind an EC2 instance.
EC2 Is Not Just a Server: Understanding What Happens Behind the Scenes
When I first started learning AWS, I thought launching an EC2 instance simply meant creating a server.
But after learning AWS networking, I realized that EC2 is only one part of a bigger system. Components like VPC, Subnet, Security Group, Internet Gateway, routing, and IP addresses work together to provide connectivity.
🔹 What is Amazon EC2?
Amazon EC2 (Elastic Compute Cloud) provides virtual machines in the AWS Cloud.
We can use EC2 to run websites, APIs, applications, Docker containers, and many other workloads.
So, is EC2 a server?
It behaves like a server, but technically it is a virtual machine running on AWS infrastructure.
It behaves like a server, but technically it is a virtual machine running on AWS infrastructure.
🔹 Where Does EC2 Live?
An EC2 instance is launched inside a VPC (Virtual Private Cloud).
Think of a VPC as your own isolated network inside AWS.
VPC: 10.0.0.0/16
|
└── Subnet: 10.0.1.0/24
|
└── EC2
Private IP: 10.0.1.10
|
└── Subnet: 10.0.1.0/24
|
└── EC2
Private IP: 10.0.1.10
A Subnet is a smaller network inside the VPC. It can be designed as public or private depending on how routing and access are configured.
🔹 IP Address & Security Group
An EC2 instance normally has a private IP for communication inside the VPC. It may also have a public IPv4 address for internet connectivity.
A Security Group works like a virtual firewall. For example:
HTTP → Port 80
HTTPS → Port 443
SSH → Port 22
HTTPS → Port 443
SSH → Port 22
We can restrict SSH access to trusted IP addresses instead of allowing everyone.
🔹 What Does an Internet Gateway Do?
An Internet Gateway (IGW) provides a path between a VPC and the internet.
But having an IGW alone doesn't automatically make an EC2 instance internet-accessible. Routing, IP addressing, subnet configuration, and Security Group rules must also allow the traffic.
🔹 Putting Everything Together
A simplified architecture looks like:
INTERNET
|
↓
Internet Gateway
|
↓
VPC
|
Subnet
|
EC2
|
Security Group
|
Web Application
|
↓
Internet Gateway
|
↓
VPC
|
Subnet
|
EC2
|
Security Group
|
Web Application
Each component has a different role:
Component| Simple Meaning
EC2| Virtual machine
VPC| AWS network
Subnet| Smaller network inside VPC
Private IP| Internal network address
Public IP| Internet-facing address
Security Group| Controls allowed traffic
Internet Gateway| Provides internet connectivity
EC2| Virtual machine
VPC| AWS network
Subnet| Smaller network inside VPC
Private IP| Internal network address
Public IP| Internet-facing address
Security Group| Controls allowed traffic
Internet Gateway| Provides internet connectivity
🔥 Final Takeaway
Don't think:
«"I launched an EC2, so my server is automatically available on the internet."»
Instead, think:
EC2 + VPC + Subnet + Routing + IP + Security Group + Gateway = Network Connectivity
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article