This Evaluation Guide uses the following network structure and instances.
In AWS, these components can be defined as per the diagram below. One important aspect in AWS is that you need to create a subnet for each Availability Zone. Because the instances are distributed on different Availability Zones, these instances are assigned to different subnets.
Components listed in this diagram are listed in the following table:
| VPC | LK-VPC | IPv4 CIDRs | 10.20.0.0/16 |
| Subnet |  Common values across subnets |
VPC assignment | LK-VPC |
| Auto-assign public IP | Yes | ||
| LK-subnet-1 | IPv4 CIDR | 10.20.1.0/24 | |
| LK-subnet-2 | IPv4 CIDR | 10.20.2.0/24 | |
| LK-subnet-3 | IPv4 CIDR | 10.20.3.0/24 | |
| Internet Gateway | LK-IGW | VPC association | LK-VPC |
| Route Table | LK-RouteTable | Subnet association | LK-public-subnet |
| Destination=10.20.0.0/16 | local | ||
| Destination=0.0.0.0/0 | LK-IGW | ||
| Security Group | LK-SG | Type=All traffic | Source=LK-SG |
| Type=SSH | Source=Your Office’s WAN IP | ||
| Instances | Common values across instances |
VPC | LK-VPC |
| Security Group | LK-SG | ||
| Source/Dest Checking on a network interface (ENI) | Disabled | ||
| node-a | Subnet | LK-subnet-1 | |
| Private IP Address | 10.20.1.10 | ||
| node-b | Subnet | LK-subnet-2 | |
| Private IP Address | 10.20.2.10 | ||
| node-c | Subnet | LK-subnet-3 | |
| Private IP Address | 10.20.3.10 |
The following sections step through the processes necessary for creating these network components, beginning with the first instance.
Post your comment on this topic.