AWS Site To Site VPN - Extended connectivity
HTML-код
- Опубликовано: 29 июн 2024
- [Note] With Amazon Linux 2023 AMI, you may not be able to install OpenSwan. So refer this new guide s3.ap-south-1.amazonaws.com/w...
For the video, you can check my course www.awswithchetan.com/courses...
---------------------------------------------
In this video, we will setup Openswan VPN server as a NAT so that other instances in the customer network can also access the VPN connection and route traffic through this NAT instance.
If you liked this video, check this out www.awswithchetan.com/courses...
Thank you!
~Chetan
Email: awswithchetan@gmail.com 
Наука
Hi All, those interested in understanding AWS Networking in depth may want to enroll in AWS Networking course of mine at www.awswithchetan.com
If you are a student, fill this short form and receive additional discount: forms.gle/z8mBsmdpDRN2FXe69
Thank you and see you there !
Thanks - Great job explaining - Been struggling for days on understanding this concept. Very clear now, with your demo.
All videos in the series are simply awesome from all angles, not sure the one dislike is for what, probably the guy himself creating similar videos and could not produce the same quality and felt jealous and disliked in frustration- haha.
Excellent videos, thanks!!!
Excellent Session man! - thank you so much
Excelente it’s so helpful, thank u so much!
Excellent Video. Both Parts.
Seriously you guys are awesome!!!
Good presentation. Watched both videos
Awesome job man...Thank you very much.
you done really nice video please make more videos on all AWS services
Thank you a lot, wish you the Best!!!!
Thanks once again.
Thank you explained well
Excellent video
good video. have a question on the new network you added. is being natted at the OPENSWAN ec2 router? or is it being passed thru to the AWS network with the original ip address of 10.200.1.x? if passed thru why no modification to the S2S VPN?
Hi I have a one query , we want to make tunnel between aws to aws but issue is that both side private ip CIDR is matched so is it possible to use Nat technology. On firewall i am able to perform this..pleas help I need urgent support
hi sir great video , deserves a subscribe , just a noob question is this setup 2 way routing ? like VPC A can also ping Subnet networks of VPC B?
Hi sir, i have the same diagram as yours and followed your video. However, i am unable to ping from the EC2 instance in the corporate network to the AWS EC2 instance in the AWS public cloud. From the EC2 instrance in the corp network, I can ping the OpenSwan. I can also ping from Openswan to the EC2 instance in the AWS public cloud. Can you pls share some troubleshooting steps? Really appreciate your help.
Hi Chetan-sir, my EC2 instance server in the on-prem can ping the CGW and it's network interface ID but unable to ping the EC2 instance in the AWS cloud. I suspect my CGW is not doing NAT properly or the CGW is not passing the traffic from my EC2 instance to the EC2 in the AWS cloud. I appreciate anyone assistance. Thank you!
Dear Chetan,
thank you for this amazing video. I am trying to use EC2 B machine as a router to openvpn subnet. I sucessfully conected my vpc A to my vpc B with AWS site to site VPN and thanks to your first video. I can SSH to EC2 A instance et I can ping EC2 B instance throug the Ipsec Tunnel. But I would like to give access to internet to my EC2-A using EC2-B as a router not to ECZ-C but to internet.
Do you have any idea to help me ?
A warm thank you !
If EC2-B is already set up as router which can NAT the egress traffic to the internet then on EC2-A subnet you need to modify the route table to route 0.0.0.0/0 to VGW. However as soon as you do that your ssh session will terminate (if your EC2 is in Public subnet). You then would have to have another jump host in VPC-A and from there need to ssh to EC2-A and test egress to internet from EC2-A.
I followed part 1 to setup a S2S VPN connection, and the client could use the configuration file to make the Tunnel 1 up, and it is stable. However, they cannot ping the EC2 instance that has been created on the same subnet to the route table and this VPN Connection has been set up. The client is asking for a Public IP, so I set the Auto-assign on for the EC2 instance during creation time. The client cannot ping either (both the Private IP of the instance as well as the public). What might be missing from my side or the client side? I have allowed All TCP and All ICMP-IPv4 traffic in the security group for the client, and attached that security group to the EC2 instance.
Hi Mo,
Not able to understand the entire network arch you have mentioned. What is client here? If you could share a small diagram, that may help.
Sir have you real time projects. So that I can get a job , because I have got training for aws.because every company demands experienced person.
in this case the router does not NAT, it bridges. i checked tcpdump. in production environment i expect NATing