

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
Click to play video
Before we can do much else on AWS, we need a network "box" to put cloud resources into. AWS calls this box a VPC, or Virtual Private Cloud.
This box (the VPC) is really just a group of IP addresses within a region we choose.
Sometimes we want multiple VPCs, for example to separate production resources from development servers. Or we might want some servers in a primary location and others in a backup region.
Running out of addresses is not fun. The only thing worse is bike shedding with a fellow engineer about what "the perfect amount" is. It's best to aim for what you need plus a bit of a buffer. Adding new addresses later isn't as annoying as it used to be.
During this course, the infrastructure we create will be for a fictional company you've recently joined called PatientPing. It's a patient management application for local doctors and dentists. It allows them to keep track of appointments, schedule follow-ups, send automated reminders, etc.
Cost check: There are no costs associated with empty VPCs, huzzah!
Create a VPC named patientping with CIDR 10.0.0.0/22.
patientping as the name tag10.0.0.0/22Run and submit the CLI tests.
If you want to use the AWS CLI instead:
aws ec2 create-vpc \
--cidr-block '10.0.0.0/22' \
--tag-specifications "ResourceType=vpc,Tags=[{Key=Name,Value=patientping}]"