- All right, now let's run through a demo
where we'll create a VPC.
You can see that I'm logged into the console.
From here, I'm going to, now I could scroll down here
to the networking section, or from the top,
I could click the services menu,
and it would be listed,
all of the services are listed alphabetical,
so there is VPC on the right.
I could also come here to networking and choose VPC.
So I'm gonna go there to VPC.
Now here at the VPC dashboard,
you can see I have one VPC.
I have one subnet, one NACL, one internet gateway,
and one route table.
Now one thing I want to point out here,
you can see I have a VPC here in this particular region,
in the Oregon region.
Remember that VPCs are specific to a region.
The subnets inside of that VPC
will be specific to the availability zone.
So you can see I have one subnet already created.
Within this region, I've already deleted the default VPC,
so I'm gonna switch regions just real quick to show you.
I'm gonna switch over to the Ohio region.
Doesn't really matter, any region would do.
And you'll see that here is what we call the default VPC.
This is default because it comes with your account.
As soon as your create you account,
you already have this default VPC.
Amazon does that as a way to just make,
lower the barrier to entry.
It makes things a whole lot easier,
especially for developers and folks
who don't have a whole lot of knowledge and experience
with networking.
They just want to launch EC2 instances
and get something running.
So the default VPC is there for that reason.
But I want to create one with a different IP range
and have a bit more control over how it's actually created.
So from here, I'm just going to say create VPC,
I'm going to name it AWS live lessons,
perhaps we'll put some applications in here later.
Now the CIDR block, this is up to us,
and generally when we're creating VPCs,
depending on how we want to segment
between applications or department,
we need a strategy for handling our ranges.
So for this one, I'm just going to choose
something like ten dot two dot zero dot zero slash 16.
Probably a whole lot more IP addresses than I'll need,
but that's okay.
So I'm gonna hit create,
and it takes it, sometimes it takes it
a few seconds to create that necessary resource.
You will see that here I have two VPCs now,
the default VPC which is always one seven two three one,
and then of course the VPC that I just created.
We could go over here and filter by VPCs.
I'm gonna choose that one and you'll see now,
because we're filtering, that only the VPC
that I just created shows up.
You will see now that this VPC does not have any subnets.
It does have a default route table,
so if we look at that, we will see that we are routing
the ten two zero zero 16 to local within the VPC,
so that's essentially our default route table.
We will also see that down here our network ACLs
that we have a network ACL for that VPC,
and the network ACL that we get by default
allows all incoming traffic and allows all outgoing traffic.
So that is creating a VPC within Amazon Web Services.