Back to Syllabus
AWS Certified Solutions Architect – Associate (SAA-C03)
Lesson 2: Module 2: Designing Multi-AZ Virtual Private Clouds (VPC)
Module 2 of 3
•
35 mins
Module 2: Designing Multi-AZ Virtual Private Clouds (VPC)
Virtual Private Cloud (VPC) Deep Dive
Amazon Virtual Private Cloud (Amazon VPC) allows you to provision a logically isolated section of the AWS Cloud where you can launch AWS resources in a virtual network that you define.
Step-by-Step VPC Architecture Setup
- Choose CIDR Block: Best practice is using RFC 1918 private IPv4 blocks, such as
10.0.0.0/16(65,536 available IP addresses). - Subnet Division: Divide the CIDR into public and private subnets across multiple AZs:
- Public Subnet AZ-A:
10.0.1.0/24 - Public Subnet AZ-B:
10.0.2.0/24 - Private Subnet AZ-A:
10.0.10.0/24 - Private Subnet AZ-B:
10.0.20.0/24
- Public Subnet AZ-A:
- Internet Gateway (IGW): Attach one IGW to your VPC and update the public route table:
0.0.0.0/0 -> igw-xxxxxx. - NAT Gateway: For backend database instances in private subnets needing outbound internet access for patches, deploy a managed NAT Gateway in a public subnet and point private route tables to it.
# AWS CLI Sample: Create VPC and Subnet
aws ec2 create-vpc --cidr-block 10.0.0.0/16 --tag-specifications "ResourceType=vpc,Tags=[{Key=Name,Value=HozalProductionVPC}]"
aws ec2 create-subnet --vpc-id vpc-0123456789 --cidr-block 10.0.1.0/24 --availability-zone us-east-1a 💡 Exam Tip & Blueprint Focus:
Ensure you practice this architectural configuration in your sandbox account. Questions on AWS, Azure, and Security+ exams frequently test failure scenario remediation and least-privilege policies.