In the VPC interface
In the Create subnet interface
Implement subnet settings
Public Subnet 1
10.10.1.0/24
according to architecture descriptionFollow the same steps to create more subnets
You can see there is 2 columns Availability Zone and Availability Zone ID. To avoid EC2 resources being used unevenly, (we tend to use AZ a to run primary and AZ b to stand by for example) AWS will randomly assign * Availability Zone into Availability Zone ID*. We can understand that Availability Zone is an alias, and Availability Zone ID is the identifier. For example, in the image above, Availability Zone ap-southeast-1a is assigned the Availability Zone ID apse1-az2. In another AWS account, the Availability Zone ap-southeast-1a may have an Availability Zone ID of apse1-az1.
Another point worth noting is that the subnets are the same, through configuring the routeing table and allocating a public IP address that we have just divided into Public and Private Subnet.
In the VPC interface
Under Auto-assign IP settings