A fintech startup company is developing a product on the AWS platform. To speed up the development, the company plans to use a SaaS provided by AWS Marketplace. The SaaS provider already configured an AWS PrivateLink. In the company’s VPC, which configuration is required to utilize this private connection so that traffic flows to the service provider over private AWS networking rather than over the Internet?

Answer options:

A.In the VPC, configure an interface VPC endpoint for the SaaS which creates an elastic network interface in the subnet with a private IP address.
B.Configure a site-to-site VPN connection in customer VPC for the SaaS to use the AWS private link connection.
C.In the VPC, set up a gateway VPC endpoint for the SaaS which creates an elastic network interface in the subnet with an elastic IP address.
D.In the VPC, create an AWS Direct Connect connection for the SaaS to securely connect with the AWS PrivateLink.

Answer – A
AWS Direct Connect enables you to directly interface your on-premises network with a device at an AWS Direct Connect location. You need to configure a Public Virtual Interface AND configure on-premises routing to utilize the direct connect for AWS public-facing services. Each virtual interface needs a VLAN ID, interface IP address, ASN, and BGP key. See the image below.
Option A is CORRECT because, as mentioned above, it creates a public virtual interface to connect to the S3 endpoint.
Option B is incorrect because to connect to the S3 endpoint a public virtual interface needs to be created, not VPN.
Option C is incorrect because to connect to the S3 endpoint a public virtual interface needs to be created, not private.
Option D is incorrect because this setup will not help to connect to the S3 endpoint.
For more information on virtual interfaces, please visit the below URL-
http://docs.aws.amazon.com/directconnect/latest/UserGuide/WorkingWithVirtualInterfaces.html