Let's deploy an Internet-connected network in Amazon Web Services! Part 2: Subnet
The elephant in the room
I shared part one of this tutorial nearly two months ago. Mega apologies!
For what it’s worth, I’m happy with my excuse.
Recapping what we have
This is part two in my series guiding you through the creation of a VPC with Internet connectivity. Last time we started looking at deploying this network:
If you’re following along then you’ve already deployed the VPC. Today, we’ll deploy the subnet.
Log in to AWS and check you’re in the correct Region
Subnets must be created in the same Region as the Virtual Private Cloud that you want to attach them to.
Not sure what a Region is? Check out What are Amazon Web Services Regions? then come back when you’re ready.
So, let’s start by confirming that we’re in the correct Region by checking if we can see the VPC we created last time.
Open the VPC Dashboard.
Click on Your VPCs on the left to see all the VPCs you have in this Region. Here, I can see the VPC named
If you can’t see the VPC you created last time, try switching to a Region that you might have used last time.
And if you really can’t find it, go ahead and create a new one. At the time of writing, AWS doesn’t charge for VPCs – and it’s unlikely they ever will. Remember, they bundle a bunch of VPCs in with new accounts. Wouldn’t that be cruel, to charge you for things that came bundled in?
Creating the subnet
Now that you’re sure that you’re in the same Region as your VPC, we can create the subnet.
Click on Subnets on the left of the VPC Dashboard.
You’ll probably see a few subnets already because AWS made some for you and attached them to the default VPCs. You can ignore these because we’re going to make our own awesome subnet.
Click on the Create subnet button at the top of the page, and you’ll see a form like this:
The details are largely up to you.
- Name tag can be anything you want. I’ve gone for
- VPC needs to be the VPC that you created last time. You don’t need to type in the ID; click in the box to see a drop-down list of the VPCs you can choose from. If you don’t see your VPC, check again that you’re really in the same Region!
- Availability Zone can be left on the default of No preference.
- IPv4 CIDR block is the value you’d normally need to think the most about. Remember, CIDR blocks describe a range of IP addresses, so you’ll want to plan ahead to figure out how many subnets you’ll want in your VPC and how big you want them to be. For this one, though, just stick in
10.0.0.0/24. This’ll give us the range
10.0.0.255, which is all we need for this tutorial.
Need a refresher on CIDR blocks and IP ranges? Check out IP addresses and CIDR blocks.
You don’t need to know what an Availability Zone is for this tutorial, but check out What are Amazon Web Services Availability Zones? if you’re interested.
Here’s the subnet I’m going to create:
Click Create to create it
There we go!
Alright! So now we have a VPC and a subnet.
To echo the question and answer at the end of the previous post, what can you do with it? Well… not much.
Next week, we’ll set up the routing so that we can launch a compute instances (or, virtual machine) on that subnet and connect to it.
See you next week!