

0 / 2 embers
0 / 3000 xp
click for more info
Complete a lesson to start your streak
click for more info
Difficulty: 4
click for more info
Not enough gems
Cost: 6 gems
1: Virtual Private Cloud (VPC)
incomplete
2: CIDR Blocks
incomplete
3: Subnetting
incomplete
4: Internet Gateways (IGW)
incomplete
5: Route Tables
incomplete
6: Private Subnets
incomplete
Back
ctrl+,
Next
ctrl+.
This lesson's interactive features are locked, please to keep using them
To do anything useful with our VPC, we need to divide it into smaller networks called subnets. This lets us create things like:
Each subnet is connected to an Availability Zone (AZ), which is one or more physical AWS data centers in a region. If we put our subnets in different AZs, a power outage affecting one AZ should not affect the other.
Once upon a time we decided to test our datacenter generators and failover. So we flipped the big red switch... only to discover that no one had filled up the diesel tanks. That was an exciting day.
Let's split our VPC CIDR, 10.0.0.0/22, into four subnets, with half in Availability Zone a and the other half in Availability Zone b.
| Name | Size | Availability Zone |
|---|---|---|
| patientping-private-a | 10.0.0.0/24 | a |
| patientping-private-b | 10.0.1.0/24 | b |
| patientping-public-a | 10.0.2.0/24 | a |
| patientping-public-b | 10.0.3.0/24 | b |
Each of these subnets will have 256 IP addresses: from 10.0.0.0 to 10.0.0.255, from 10.0.1.0 to 10.0.1.255, etc.
PatientPing needs you to split our VPC into four subnets.
Cost check: Empty subnets don't cost anything.
Run and submit the CLI tests.
If you want to use the CLI instead, here's the command structure:
aws ec2 create-subnet \
--vpc-id VPC_ID \
--cidr-block CIDR \
--availability-zone AZ_NAME \
--tag-specifications 'ResourceType=subnet,Tags=[{Key=Name,Value=SUBNET_NAME}]'