Hey there, I just wanted to say that your videos and hands-on demos are truly awesome! 👏 While watching, I noticed a couple of things: At around 14:16, you mentioned that a VPC is private and only allows private IPv4 ranges. However, it's worth noting that while it's technically possible to create such a VPC in AWS, it's generally not recommended due to potential routing issues. During the demo for the Bastion Host at 54:56, you encountered a permission/access denied error. Although you continued with the demo, it might be helpful to address such errors promptly to ensure a smoother learning experience. I hope you find this feedback helpful! It's intended to improve the overall quality of your content, not to nitpick. Keep up the great work! 🚀
Thanks so much for this. However, i think the bastion host did not get connected to the private instance. I suspect its because the key pair permission is too open.
Bro you never connected to private instance through bastion host, check your video on again(1:03:09) and (54:37) where it's showing permission denied, carefully see the error and the terminal you are on.
The video is very good!. Thanks for your effort to make this video. But at about 1:03:15, either NAT not setup properly or key pair file had some issue, the SSH from Baston instance to private instance failed. Your ping was performed from Baston server not from the private instance.
good video but there is a bad info about ssh private key , it should be chmod 400 so your test was not ok. I watched the video until 1h03min. :) may be after you discovered this
I think no have noticed at 55.10 when you are trying to doing ssh from baston host to private the connection has not been established but ya if we give 400 to key definitely it would have connected but ya it's okay... Just a key permission issue nothing else
@@peaceofcode are baba aapne diya 777 but permission denied aa raha.. Still hm private instance p ni gye.. If you see still we can see public ip of public instance if we are doing ssh -I privatekey hostname@privateip then jb hm logged in hoenge it should show private ip but muje aisa lag raha we are still in public instance..
Man, you killed it. I feel like a pro in VPC now! BTW you need to teach us how to learn new topics (Basically, how you approach when you want to learn a completely new topic. Whether you go for the videos on the topics/ blogs/ documentation). Just wanna know the right approach😅
Thanks glad I was of help, and as for the approach I use a mix of videos and documentations to understand a specific topic, but it depends if you like understanding through videos then its also fine because there are a lot of videos regarding a topic out there!!
Aws site-to-site VPN VPN gateway customer gateway direct connect virtual private gateway make some videos these topics Really video is very informative
Hi, when you tried ssh from your bastion it didn't connect your permissions to the key file was wrong it should be 400 read only permission for the pem key.
Awesome and so detailed. Really thanks for making video and explained it in such a easy way. Please upload more videos like on AWS Security services or secure architecture.
Aakash, thanks so much for this video - it's exactly what I needed. It was easier to follow and understand than Stephane Maarek's similar lecture on Udemy. You have a nice way of breaking things down and making them easy to understand. The only thing missing is a clean-up section to walk us through deleting everything for those who followed along and did the steps. Looking forward to seeing more of your videos!
55:00 accessing the private instance via baston instance is failed please check it and revise and also 1:43:00 in prod vpc 's routing table the ip adddress should be 172.31.0.0/16 so it can be in same network
I don't know how the first part of the video was working for you but I am getting this error when trying to connect to EC2 No public IPv4 address assigned With no public IPv4 address, you can't use EC2 Instance Connect.
