Welcome to waturrr! Open the hamburger menu to select a channel!
OFFICIAL ARTICLE READER
◀BACK TO ARCHIVE

AWS VPC Peering: Connecting Isolated Virtual Networks

DATE: 2026-11-13BY: WATURRR

Overview of the Build

I completed this project over 56 minutes of hands-on work in the ap-south-2 region, building an isolated virtual network architecture and launching a virtual server. I created 1 VPC, configured subnets, and provisioned a virtual server instance. Project Link: View Project on NextWork

Tech Stack

  • ▶AWS VPC: Reviewed and configured route tables, subnets, gateways, and peering connection forms.
  • ▶Amazon EC2: Managed compute instances, Elastic IPs, and server configuration.
  • ▶EC2 Instance Connect: Established secure browser-based SSH terminal connections.

Project Highlights

  • ▶Created 1 VPC using the Create VPC form in the VPC console, establishing an isolated virtual network in ap-south-2.
  • ▶Configured network peering connections and updated route tables to route traffic securely across networks.
  • ▶Allocated and associated Elastic IP addresses in the EC2 console for static public IP access.
  • ▶Audited subnet details, Network ACLs, and security groups to review inbound rules and network firewall policies.
  • ▶Launched EC2 Instance Connect and verified cross-network reachability using the ping terminal command.

Steps I Took

  • ▶Step 1: VPC Console Access - Opened the VPC service from the console home page, navigated to Your VPCs, and opened the Create VPC form.
  • ▶Step 2: VPC Creation - Provisioned the VPC and verified configuration parameters on the VPC details page.
  • ▶Step 3: Network Configuration - Completed configuration settings and CIDR allocations across the VPC list.
  • ▶Step 4: Peering Connection Setup - Filtered by the VPC, navigated to peering connections, and opened the Create peering connection form.
  • ▶Step 5: Route Table Configuration - Opened route tables, navigated to edit routes, and updated route table details to direct traffic.
  • ▶Step 6: EC2 Service Navigation - Switched to the EC2 service, opened the instances management page, and opened the Launch an instance form.
  • ▶Step 7: Instance Provisioning - Filled in the Launch an instance form and returned to the instances list to monitor deployment.
  • ▶Step 8: Elastic IP Allocation - Opened the Elastic IPs page and navigated through the allocate and associate Elastic IP address workflows.
  • ▶Step 9: Security Review - Opened subnet details, navigated to Network ACLs to edit inbound rules, and reviewed security groups.
  • ▶Step 10: Connectivity Validation - Opened the connect to instance page, launched EC2 Instance Connect, and verified network reachability with ping.
  • ▶Step 11: Architecture Verification - Reviewed NAT gateways, subnets, Internet gateways, route tables, and security groups from the VPC console.