AWS VPC peering same in region | How to create vpc peering in same region

AWS VPC (Virtual Private Cloud) Peering allows two VPCs to communicate with each other privately using private IP addresses. This is useful for connecting resources across VPCs in the same AWS account or between different AWS accounts. Here's how you can set up VPC peering in the same AWS region:

Steps to Set Up VPC Peering in the Same Region
Step 1: Create a VPC Peering Connection
Log in to the AWS Management Console.

Navigate to the VPC Dashboard.

In the left navigation pane, select Peering Connections and click Create Peering Connection.

Specify the following:

Peering Connection Name: Provide a name for the connection.
Requester VPC: Select the VPC initiating the peering connection.
Accepter VPC:
If within the same account, select another VPC from the dropdown.
If in another AWS account, specify the AWS Account ID and VPC ID.
Click Create Peering Connection.

Step 2: Accept the Peering Request
If the accepter VPC is in the same AWS account:
Go to Peering Connections.
Locate the newly created request and click Actions → Accept Request.
If the accepter VPC is in another AWS account:
The account owner must log in, navigate to Peering Connections, and accept the request.
Step 3: Update Route Tables
To enable communication between the two VPCs, update their route tables:

Go to the Route Tables section of the VPC Dashboard.
Select the route table associated with the subnets that need connectivity.
Add a route:
Destination: The CIDR block of the peered VPC.
Target: The peering connection ID.
Save the changes.
Repeat this step for both VPCs.

Step 4: Update Security Groups
Modify the security groups to allow traffic between the VPCs:

Go to the Security Groups section.
Edit inbound and outbound rules:
Add rules that allow traffic to and from the CIDR block of the peered VPC.
Step 5: (Optional) Verify Connectivity
Launch EC2 instances in each VPC.
Use a tool like ping or SSH to verify connectivity between the instances using private IP addresses.
Key Considerations
Overlapping CIDR Blocks: VPC peering does not support overlapping IP ranges.
No Transitive Peering: A VPC peered to one VPC cannot communicate with another VPC through that connection.
Regional Restriction: The peering connection is limited to the same AWS region unless it's an inter-region VPC peering.