> ## Documentation Index
> Fetch the complete documentation index at: https://docs.briankimemia.is-a.dev/llms.txt
> Use this file to discover all available pages before exploring further.
# Vpcpeering
# π οΈ Legendary AWS VPC Peering Project
Welcome to the **Legendary AWS Networks VPC Peering Project**! This detailed guide will walk you through the process of creating secure, private communication between two isolated Virtual Private Clouds (VPCs) in AWS. We'll use Terraform to automate the entire process while ensuring scalability, efficiency, and best practices.
***
## π Project Overview
In this project, we will:
1. **Provision two VPCs** with unique CIDR blocks.
2. **Establish a VPC Peering connection** between the two VPCs.
3. **Update route tables** to allow traffic flow between the VPCs.
4. **Launch EC2 instances** in both VPCs for connectivity testing.
5. **Test private communication** between instances in separate VPCs.
6. **Optionally clean up resources** after testing.
πΉ **Key Concept:**\
VPC Peering allows secure, private communication between two isolated networks without using the public internet.
***
## π£οΈ Process Flow
Here's a visual flowchart of the VPC Peering setup process:
```mermaid theme={null}
graph TD
Start[ποΈββοΈ Project Start: AWS VPC Peering Setup]:::start
Start --> Step1[βοΈ Step 1: Provision VPCs]:::step
Step1 --> VPC1[π¦ VPC 1 - CIDR: 10.1.0.0/16]:::vpc
Step1 --> VPC2[π¦ VPC 2 - CIDR: 10.2.0.0/16]:::vpc
VPC1 --> Subnet1[π Public Subnet in VPC 1]:::subnet
VPC2 --> Subnet2[π Public Subnet in VPC 2]:::subnet
Subnet1 --> Step2[ποΈ Step 2: Establish VPC Peering Connection]:::step
Step2 --> Requester[π€ Initiate Peering Request - VPC 1 (Requester)]:::peer
Step2 --> Accepter[π€ Accept Peering Request - VPC 2 (Accepter)]:::peer
Step2 --> Step3[π£οΈ Step 3: Configure Route Tables]:::step
Step3 --> RouteVPC1[π Add Route in VPC 1 to VPC 2 CIDR]:::route
Step3 --> RouteVPC2[π Add Route in VPC 2 to VPC 1 CIDR]:::route
Step3 --> Step4[π» Step 4: Launch Test EC2 Instances]:::step
Step4 --> EC2Instance1[π EC2 Instance in VPC 1]:::ec2
Step4 --> EC2Instance2[π EC2 Instance in VPC 2]:::ec2
Step4 --> Step5[π Step 5: Test Connectivity]:::test
Step5 --> TestPing[π‘ Ping Test Between Instances]:::test
TestPing --> Success[β
Connectivity Verified]:::success
Success --> Complete[π Project Complete: Secure Private Connection]:::complete
Complete --> Cleanup[πͺ© Optional: Clean Up Resources]:::cleanup
classDef start fill:#FF9900,stroke:#333,stroke-width:2px,color:#fff;
classDef step fill:#F4F4F4,stroke:#333,stroke-width:1px;
classDef vpc fill:#00BFFF,stroke:#333,stroke-width:1px,color:#fff;
classDef subnet fill:#34D399,stroke:#333,stroke-width:1px,color:#fff;
classDef peer fill:#FBBF24,stroke:#333,stroke-width:1px,color:#fff;
classDef route fill:#A855F7,stroke:#333,stroke-width:1px,color:#fff;
classDef ec2 fill:#10B981,stroke:#333,stroke-width:1px,color:#fff;
classDef test fill:#6366F1,stroke:#333,stroke-width:1px,color:#fff;
classDef success fill:#22C55E,stroke:#333,stroke-width:2px,color:#fff;
classDef complete fill:#FF6363,stroke:#333,stroke-width:2px,color:#fff;
classDef cleanup fill:#D1D5DB,stroke:#333,stroke-width:1px;
```
***
## π οΈ Step-by-Step Guide
### βοΈ Step 1: Provision VPCs
1. **Create two VPCs** with the following CIDR blocks:
* **VPC 1**: `10.1.0.0/16`
* **VPC 2**: `10.2.0.0/16`
2. Enable DNS resolution and hostnames for both VPCs.
3. Configure **public subnets** in each VPC to allow external access.
π¨ Ensure the CIDR blocks do not overlap to avoid routing conflicts!
***
### ποΈ Step 2: Establish VPC Peering Connection
1. **Initiate the VPC Peering request** from VPC 1 (Requester).
2. **Accept the request** in VPC 2 (Accepter).
3. Verify that the peering connection status is `active`.
***
### π£οΈ Step 3: Configure Route Tables
1. Update the **route table in VPC 1**:
* Add a route to direct traffic to VPC 2βs CIDR (`10.2.0.0/16`) via the peering connection.
2. Update the **route table in VPC 2**:
* Add a route to direct traffic to VPC 1βs CIDR (`10.1.0.0/16`) via the peering connection.
π‘ **Best Practice:**\
Use descriptive names for your route tables and rules to simplify management.
***
### π» Step 4: Launch Test EC2 Instances
1. Launch an **EC2 instance** in each VPC:
* **VPC 1 Instance**: Amazon Linux 2, Public Subnet
* **VPC 2 Instance**: Amazon Linux 2, Public Subnet
2. Assign **security groups** to allow ICMP (ping) traffic between instances.
***
### π Step 5: Test Connectivity
1. Use **EC2 Instance Connect** to SSH into the EC2 instance in VPC 1.
2. Run a `ping` test to the private IP address of the EC2 instance in VPC 2.
3. Ensure successful connectivity:
* **Output**: Packets transmitted successfully.
πΉ **Troubleshooting:**\
If the ping test fails, check security group rules and route table configurations.
***
### πͺ© Cleanup (Optional)
If youβre done testing:
1. **Delete the VPC peering connection**.
2. Terminate the EC2 instances.
3. Remove route table entries.
4. Delete the VPCs to avoid incurring charges.
π¨ **Important:**\
Ensure all resources are deleted to prevent unnecessary AWS billing.
***
## π Highlights
* **Automation**: Use Terraform to automate the entire process.
## π§ Contact
For questions or feedback, reach out:
π¨ Email: [projects@briankimemia.is-a.dev](mailto:projects@briankimemia.is-a.dev)
π Portfolio: [Brian Kimemia](https://briankimemia.is-a.dev/)
**GitHub:** [BrianKN019](https://github.com/BrianKN019)
***
**Thank you for exploring this project! Letβs innovate and build secure AWS solutions together. π**