Select Subnet
Select Create subnet


Subnet name, enter ``` PublicSubnet-OnPremise**
Select AZ us-ease-1a
Ipv4 CIDR block , enter 10.12.1.0/24
Scroll down and click Create subnet*
4. Complete creating subnet







You can see there are 2 columns, Availability Zone and Availability Zone ID. To avoid EC2 resources being used unevenly, (we often tend to use AZ a to run primary and AZ b to stand by, for example), AWS will randomly assign Availability Zone to ** Availability Zone ID**. We can understand that Availability Zone is a form of alias, and Availability Zone ID is the identifier. For example, in the image above Availability Zone ap-southeast-1a is assigned Availability Zone ID as apse1-az2. In another AWS account, Availability Zone ap-southeast-1a might have an Availability Zone ID of apse1-az1.

Select Enable auto-assign public IPv4 address
Click Save

The same is done with PublicSubnet-Provider
Select PublicSubnet-OnPremise , select Actions, select Edit subnet settings
Select Enable auto-assign public IPv4 address
Click Save
Another notable point is that the subnets are basically the same. Through route table configuration and public IP address allocation, we can divide them into Public and Private Subnets.