AWS Certified Solutions Architect - Associate (SAA-C02)

Sign Up Free or Log In to participate!

VPC peering need route in route table

I just wanted to confirm since it didn’t work for me doing same as lecture mentions. I created a VPC peer connection and then I have created an EC2 on default VPC to test VPC connection and I couldn’t ping or ssh from my 10.0.0.0 vpc to default one until I have added routes to my subnet and default vpc routing table.

1 Answers

You are correct – once you have peered the VPCs and accepted the peering, you will need to add a route to each route table associated with the Subnets used by your EC2 instance. Add the IP range of the destination VPC and make sure you are updating the route table used by the subnet used by your EC2 instances.

Check that your NACLs and Security Groups will allow the ICMP request as well.

Sign In
Welcome Back!

Psst…this one if you’ve been moved to ACG!

Get Started
Who’s going to be learning?