AWS Virtual Private Cloud (VPC) is a networking service that enables you to launch AWS resources in a logically isolated virtual network that you’ve defined. This virtual network closely resembles a traditional network that you’d operate in your own data center, with the benefits of using the scalable infrastructure of AWS.

This lab will teach you how to create a custom AWS VPC with a public and private subnet. You will also learn how to create an internet gateway and route table to allow the public subnet to access the internet.

Amazon will bill you for any applicable AWS resources and time used that are not covered in the AWS Free Tier.

Part 1: Create a VPC and Subnets

VPCs are used to isolate your AWS resources from the public internet and other VPCs. They define a virtual network that closely resembles a traditional network that you’d operate in your own data center. Subnets are used to divide a VPC into multiple networks. They are used to isolate resources within a VPC from each other. Subnets can be public or private, depending on whether they are connected to the internet.

1. Go to the VPC Dashboard in the AWS console.
2. Click Create VPC.
3. Enter a Name for your VPC.

4. Enter a CIDR block for your VPC.

   When creating a VPC, it is important to choose a CIDR block that is large enough to accommodate your needs. You can use a CIDR calculator to help you choose the right CIDR block.

5. Click Create VPC.

   When creating subnets, it is important to divide your VPC into logical groups. For example, you may want to create a subnet for web servers, a subnet for database servers, and a subnet for bastion hosts.

6. Go to the Subnets page in the AWS console.
7. Click Create subnet.
8. For VPC, select the VPC you created in step 5.
9. For Subnet name, enter Public subnet.
10. For Availability Zone, select an availability zone.
11. For IPv4 CIDR block, enter a CIDR block for the public subnet.
12. Select the Enable auto-assign public IPv4 address checkbox.
13. Click Create subnet.
14. Repeat steps 7-13 to create a private subnet.

Part 2: Create Internet Gateway

15. Go to the Internet gateways page in the AWS console.
16. Click Create internet gateway.
17. For Name, enter Internet Gateway.
18. Click Create internet gateway.
19. Go to the Internet gateways page in the AWS console.
20. Select the internet gateway you created in step 18.
21. Click the Actions tab.
22. Click Attach to VPC.
23. Select the VPC you created in step 5.
24. Click Attach.

Part 3: Create Route Tables

25. Go to the Route tables page in the AWS console.
26. Click Create route table.
27. For Name tag, enter Public route table.
28. For VPC, select the VPC you created in step 5.
29. Click Create route table.
30. Go to the Route tables page in the AWS console.
31. Select the public route table you created in step 29.
32. Click the Routes tab.
33. Click Add route.
34. For Destination, enter the CIDR block 0.0.0.0/0.
35. For Target, select the internet gateway you created in step 18.
36. Click Save.
37. Go to the Route tables page in the AWS console.
38. Select the public subnet route table you created in step 29.
39. Click the Subnet Associations tab.
40. Click Add subnet.
41. Select the public subnet you created in step 9.
42. Click Save.

Part 4: Create Security Groups

43. Go to the Security groups page in the AWS console.
44. Click Create security group.
45. For Security group name, enter Public security group.
46. For Description, enter Public security group.
47. For VPC, select the VPC you created in step 5.
48. Click Create security group.
49. Repeat step 43.
50. Select the public security group you created in step 48.

51. Click the Inbound rules tab.

    Security groups are used to control inbound and outbound traffic to and from your AWS resources. You can use security groups to control traffic based on IP address, port, and protocol.

52. Click Edit inbound rules.
53. Click Add rule.
54. For Type, select SSH.
55. For Source, select My IP.
56. Click Save rules.
57. Go to the Security groups page in the AWS console.
58. Repeat steps 43-56 to create a private security group that allows SSH from the public security group.

Part 5: Create EC2 Instances

A bastion host is a server that is used to access other servers in a secure manner. Bastion hosts are typically placed in a public subnet and are configured to only allow SSH traffic from authorized IP addresses. Once you have connected to the bastion host, you can then SSH to other servers in the VPC.

57. Go to the EC2 Dashboard in the AWS console.
58. Click Launch instance.
59. Select the Amazon Linux 2 AMI.
60. Select the t2.micro instance type.
61. Click Next: Configure Instance Details.
62. For Network, select the VPC you created in step 5.
63. For Subnet, select the public subnet you created in step 9.
64. For Auto-assign Public IP, select Enable.
65. Click Next: Add Storage.
66. Click Next: Add Tags.
67. Click Add Tag.
68. For Key, enter Name.
69. For Value, enter Public EC2 instance.
70. Click Next: Configure Security Group.
71. Select the public security group you created in step 48.
72. Click Review and Launch.
73. Click Launch.
74. Select Create a new key pair.
75. For Key pair name, enter SSH key pair.
76. Click Download Key Pair.
77. Click Launch Instances.
78. Repeat steps 57-73 to create an EC2 instance in the private subnet using the private security group.

Part 6: Connect to the EC2 Instances

79. Go to the EC2 Dashboard in the AWS console.
80. Select the public EC2 instance you created in step 73.
81. Click Connect.
82. Copy the SSH command.
83. Open a terminal.
84. Paste the SSH command into the terminal.

    ssh -i "SSH key pair.pem" ec2-user@<public EC2 instance IP address>
    

85. From the EC2 instance, SSH into the private EC2 instance.

    ssh -i "SSH key pair.pem" ec2-user@<private EC2 instance IP address>
    

More Info