You work for a famous bakery who are deploying a hybrid cloud approach. Their legacy IBM AS400 servers will
remain on premise within their own datacenter however they will need to be able to communicate to the AWS
environment over a site to site VPN connection. What do you need to do to establish the VPN connection?
A.
Connect to the environment using AWS Direct Connect.
B.
Assign a public IP address to your Amazon VPC Gateway.
C.
Create a dedicated NAT and deploy this to the public subnet.
D.
Update your route table to add a route for the NAT to 0.0.0.0/0.
I guess its a typo error
It should be VPG gateway
True
Why not choose A?
’cause DX is not a VPN solution.
I agree with Prakhar Budholiya
Why not A? Direct Connect.
I have the same question. Have you sorted out?
Read the question … ” over a site to site VPN connection”
Could someone can explain the reason, why is B, not A. Thanks!
B
See some asking, why not A? Direct Connect isn’t a VPN solution, it is dedicated line from your onprem directly in to AWS.
Answer is B.
exactly!
Direct Connect include VPN connection as wel. So still I am not convinced with option B
DirectConnect is NOT a site to site VPN into your VPC. You can VPN into your DC provider but that is something entirely different.
Regarding the first comment, VPG? what is that?
Got it Virtual Private Gateway (VPG).
https://campus.barracuda.com/product/nextgenfirewallx/doc/41097886/how-to-configure-a-site-to-site-ipsec-vpn-to-the-amazon-aws-vpn-gateway/
A VPC VPN Connection utilizes IPSec to establish encrypted network connectivity between your intranet and Amazon VPC over the Internet. VPN Connections can be configured in minutes and are a good solution if you have an immediate need, have low to modest bandwidth requirements, and can tolerate the inherent variability in Internet-based connectivity. AWS Direct Connect does not involve the Internet; instead, it uses dedicated, private network connections between your intranet and Amazon VPC.