Rule: EC2 Instances Should Be in a VPC

Rule Description

Troubleshooting Steps (if applicable)

2. 1.
   Verify if the EC2 instance is already launched in a VPC.
4. 2.
   If the EC2 instance is not in a VPC, proceed with the remediation steps.

Remediation Steps

2. 1.
   Log in to the AWS Management Console.
4. 2.
   Navigate to the EC2 Dashboard.

Creating a new VPC

2. 1.
   Click on "Create VPC" button.
4. 2.
   In the "Name tag" field, provide an identifiable name for the VPC.
6. 3.
   Define the "CIDR block" for the VPC. Ensure the CIDR block does not conflict with any existing VPCs or IP ranges.
8. 4.
   Choose the tenancy option based on your requirements. (Shared or Dedicated)
10. 5.
    Click on "Create VPC" button to create the new VPC.

Configuring EC2 Instance

2. 1.
   Select the desired EC2 instance from the list or launch a new instance.
4. 2.
   In the "Configure Instance Details" section, select the newly created VPC under the "Network" dropdown menu.
6. 3.
   Choose the desired subnet within the VPC or create a new subnet within the VPC.
8. 4.
   Complete the remaining instance configuration details such as instance type, storage, security groups, etc.
10. 5.
    Review the configuration and click on the "Launch" button to launch the EC2 instance.

Verifying VPC Association

2. 1.
   Once the EC2 instance is launched, go to the EC2 Dashboard.
4. 2.
   Navigate to the "Instances" section and find the instance launched in the previous step.
6. 3.
   In the "Network Interfaces" section of the selected instance, verify that the VPC and subnet are correctly associated.

Troubleshooting (if applicable)

2. 1.
   Ensure the VPC and subnet IDs mentioned during instance launch are correct.
4. 2.
   Check if the security group assigned to the instance allows necessary inbound/outbound connections.
6. 3.
   Ensure there are no conflicts with IP ranges or CIDR blocks.
8. 4.
   Verify if the VPC's route table is properly configured to allow traffic to and from the internet or other necessary resources.