VPC - An analogy about shared resources
Public subnets and Internet Gateway
Load balancing - one front door, many clerks
<aside> 🚧
This page is currently under construction. Please check back later.
</aside>
End goal for the trainees to understand on VPC (more on Load balancing later within the same diagram)
<aside> 💭
It is recommended to refresh your memory around basics network concepts by going through Week 9 - Networking and APIs from the Core Program
</aside>
The diagram above is the destination. Rather than presenting it all at once, the sections below build it one layer at a time — each one adds a single subnet and the AWS pieces that make it work, and ends by showing you where you are in the full picture.
| Section | What it adds to the diagram | New concepts |
|---|---|---|
| VPC — An analogy | The empty building | VPC, regions, AZs, CIDR |
| Public subnets and Internet Gateway | Public subnet in AZ A + the web server | Subnets, route tables, Internet Gateway |
| Private subnet and NAT | Private subnet in the same AZ + the app server | Private routing, Bastion / SSM, NAT Gateway |
| Endpoint and security groups | Private subnet in AZ B + the database | Cross-AZ routing, VPC endpoints, Security Groups, NACLs |
| Putting it all together | The complete diagram, reassembled | Recap, request walkthroughs, self-check, cleanup |
The HackYourFuture curriculum is licensed under CC BY-NC-SA 4.0 https://hackyourfuture.net/

Built with ❤️ by the HackYourFuture community · Thank you, contributors
Found a mistake or have a suggestion? Let us know in the feedback form.