In the VPC Interface:
In the Create subnet Interface:
Implement Subnet Settings:
Public Subnet 1
10.10.1.0/24
according to the architecture descriptionFinish Creating Subnet
Follow the same steps to create more subnets:
10.10.2.0/24
located in Availability Zone ap-southeast-1b10.10.3.0/24
located in Availability Zone ap-southeast-1a10.10.4.0/24
located in Availability Zone ap-southeast-1bNote: You can see there are 2 columns: Availability Zone and Availability Zone ID. To avoid uneven usage of EC2 resources (for example, using AZ a for primary and AZ b for standby), AWS randomly assigns Availability Zone into Availability Zone ID. Availability Zone is an alias, and Availability Zone ID is the identifier. For instance, in the image above, Availability Zone ap-southeast-1a is assigned the Availability Zone ID apse1-az2. In another AWS account, Availability Zone ap-southeast-1a may have an Availability Zone ID of apse1-az1.
Tip: Another important point to note is that even though the subnets are the same, configuring the routing table and allocating a public IP address allows us to distinguish between Public and Private Subnets.
In the VPC Interface:
Under Auto-assign IP settings:
Repeat the same process for Public subnet 2.