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.
Q. How does AWS Direct Connect differ from an IPSec VPN Connection?
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.
Q. Can I use AWS Direct Connect and a VPN Connection to the same VPC simultaneously?
Yes. However, only in fail-over scenarios. The Direct Connect path will always be preferred, when established, regardless of AS path prepending.
Q. Can I establish a Layer 2 connection between VPC and my network?
No, Layer 2 connections are not supported.
0
0