Turning down the Cloud complexities into a clear sky || Cloud and DevOps Enthusiast ☁️ || AWS || Technical Blogger 🖋|| B-tech CSE💻
Welcome to my corner of the cloud, where ideas scale faster than servers and downtime is not an option! Here, I write about everything from spinning up VPCs to tearing down myths about the cloud. Whether you’re an engineer, a curious learner, or someone who just likes seeing words like 'serverless' and 'auto-scaling,' you’re in the right place. Consider this blog your high-availability zone for tips, tutorials, and tech thoughts—delivered with 99.99% uptime .
Markdown supported · ⌘↵ to post
Anik Sikder
Great walkthrough, Saumya! The step-by-step guide makes connecting multiple VPCs with Transit Gateway super approachable, especially for Windows users who want to manage everything via MobaXterm.
One tip I’d add for beginners: don’t forget to check your security groups and network ACLs to ensure that SSH traffic is allowed between your EC2 instances in different VPCs. Sometimes that’s the hidden blocker for inter-VPC connectivity.
Also, for anyone trying this out consider setting up a jump host (bastion) in your public VPC as a secure gateway, which you effectively did here with the VPC 1 instance. It’s a best practice that keeps your private instances isolated yet accessible.
Thanks for sharing this will definitely help folks simplify complex AWS networking!