Internet Gateway (IGW)
Attaches to the VPC root boundary to perform 1:1 NAT mapping between private IPv4 addresses and public IPv4 addresses, and routes native IPv6 packets directly without introducing availability risks or bandwidth bottlenecks.
AWS Container Placement
VPC
Summary
Horizontally scaled, redundant, and highly available VPC component that enables communication between resources in your VPC and the internet.
When to Use (SAA-C03)
Attach one IGW per VPC that hosts public-facing resources; private-only VPCs should NOT have an IGW.
Allowed Ingress Connections & Ports
| Source Service | Protocol | Port | Architectural Rationale |
|---|---|---|---|
| WEBCLIENT | TCP, UDP, ICMP | 80, 443, 22, All | Public internet inbound traffic addressed to VPC public IPv4 or IPv6 allocations |
| NAT | TCP, UDP, ICMP | All / Ephemeral | Outbound translated packets from NAT Gateways destined for the public internet |
Allowed Egress Targets & Ports
| Target Service | Protocol | Port | Data Flow Rationale |
|---|---|---|---|
| WEBCLIENT | TCP, UDP, ICMP | All | Outbound traffic exiting the VPC directed toward internet hosts and services |
| ALB | HTTP, HTTPS | 80, 443 | Inbound web traffic dispatched to public Application Load Balancers |
| EC2 | TCP, SSH | 80, 443, 22 | Direct traffic forwarding to instances configured with public IP addresses |
Key Configuration Parameters & AWS Best Practices
| Parameter | Format / Example | Purpose & Rationale |
|---|---|---|
| VPC Association (vpcId) (Required) | vpc-0a1b2c3d4e5f67890 | The target VPC identifier to which the Internet Gateway attaches. Why: An Internet Gateway must be explicitly attached to a VPC before route tables can designate it as an active 0.0.0.0/0 route target. AWS limits each VPC to exactly 1 attached IGW. |
| Tags | Name: igw-production-main, Project: CoreNetwork | Resource tags for identification, governance, and compliance auditing. Why: Enables identification across AWS console views and automated infrastructure-as-code audits. |
Practice Labs Using Internet Gateway
Missing Internet Gateway Route
Attach or route default outbound traffic 0.0.0.0/0 to the Internet Gateway in the public route table.…
CLF-02Locked-Out Security Group Ingress
Add an inbound rule allowing TCP port 80 from 0.0.0.0/0 to the web instance Security Group.…
CLF-03Public Database Exposure Vulnerability
Move or configure RDS to be in a private subnet, disable public accessibility, and restrict ingress exclusivel…
CLF-04Single Point of Failure (Single-AZ)
Add a secondary subnet in us-east-1b and front instances with an Application Load Balancer across both Availab…
CLF-06Tight Coupling in Transaction Processing
Decouple the architecture by placing an Amazon SQS queue between the producer and consumer.…
SAA-02HealthTech EMR Backend: Asymmetric Outbound NAT Routing
Re-point the private route table default route pointing to NAT (0.0.0.0/0 -> nat-xxx) in the public subnet.…
Frequently Asked Questions
Where does Internet Gateway live inside an AWS VPC architecture?
Valid container placement: VPC. Attaches to the VPC root boundary to perform 1:1 NAT mapping between private IPv4 addresses and public IPv4 addresses, and routes native IPv6 packets directly without introducing availability risks or bandwidth bottlenecks.
When should I use Internet Gateway on the AWS SAA-C03 exam?
Attach one IGW per VPC that hosts public-facing resources; private-only VPCs should NOT have an IGW.
Can I simulate Internet Gateway packet routing without an AWS account?
Yes. CloudTracer simulates Internet Gateway along with 53 AWS services directly in your browser and exports production Terraform HCL.