Day 29: Establishing Secure Communication Between Public and Private VPCs via VPC Peering.
Hello KodeKloud Team,
I would like to request a review/re-evaluation of my AWS VPC Peering task submission.
The task was marked as failed with the message:
“VPC Peering connection does not exist.”
However, I verified the setup multiple times and confirmed that:
- VPC peering was configured between the default VPC and the private VPC.
- Route tables were updated on both sides.
- ICMP traffic was allowed in the private EC2 security group.
- SSH access to the public EC2 instance was working successfully.
- Most importantly, I was able to successfully ping the private EC2 instance from the public EC2 instance, which confirmed end-to-end connectivity.
It is possible that the validator checked before the peering connection status updated properly, or there may have been a validation issue.
Could you please verify the task again? Screenshots attached.
Thank you for your support and guidance.
Best regards,
Riyaz Khan
