From the course: Hands-On Development in AWS

Unlock this course with a free trial

Join today to access over 24,700 courses taught by industry experts.

Understanding default VPC

Understanding default VPC

- Nowadays, whenever you launch an EC2 instance, it has to be attached to a subnet that is within a VPC. So every region that you go to will have a default VPC created for you. Why? That is because VPCs are somewhat complicated. They are specific to the networking side of infrastructure as a service. So, you need to have a firm understanding of how IP subnetting works, and what a CIDR block is, and how subnets need to exist within that overall CIDR block and there needs to be a internet gateway to translate public to private addresses and whatnot. So, as I mentioned, every region will have a default VPC for you to connect EC2 instances to so that you don't have to worry about creating a VPC. Here in the VPC service, I'm in the Ohio region, and I have done nothing to manipulate my VPCs in Ohio. This default dashboard that we see here, we can see I have one VPC and three subnets. Now, because I have one VPC, we could make an assumption that these three subnets are all associated with…

Contents