Question

A financial services company already has a 10 Gbps AWS Direct Connect dedicated connection terminating at a colocation facility. The network team now needs to give an internal analytics application private, low-latency access to a third-party market-data SaaS offering that is published through AWS PrivateLink in a provider VPC. The traffic must never traverse the public internet, and the team wants to avoid provisioning a second physical circuit. Which approach lets them consume this SaaS service over their existing Direct Connect?

Accepted Answer

Create an interface VPC endpoint to the SaaS provider's PrivateLink service in the consumer VPC, then reach that VPC through a private virtual interface (private VIF) over the existing Direct Connect

Answer

Configure a public virtual interface (public VIF) on the Direct Connect and connect directly to the SaaS provider's public service endpoints

Answer

Establish a site-to-site IPsec VPN over the internet to the SaaS provider VPC and route the analytics traffic through it

Answer

Enable VPC peering between the consumer VPC and the SaaS provider VPC and advertise the peered routes over the Direct Connect