What are the benefits of using Redshift Managed VPC Endpoints vs. VPC Peering?



If I want to connect a Quicksight instance in Account A, to a private Redshift cluster (i.e. located in a private VPC subnet) in Account B, what reasons would I have to use a (more expensive from the looks of it) Redshift Managed VPC Endpoint to provide this cross-account, cross-VPC connectivity, over using VPC peering? Is this simply a case of "less management overhead", or is there a technical reason why VPC peering would not be suitable in this case?

1 Answer

VPC peering connects two networks together and allows arbitrary routing between them. Once peered, you can configure routes, security groups, and ACLs to let nodes on either network communicate over the peering connection.

Redshift VPC Endpoints use PrivateLink to allow one VPC to access resources in another VPC as if they are local to the same VPC. It is different than the peering concept of connecting two networks together. Instead, the services on the caller side can access resources (in this case, Redshift) on the endpoint side, but not vice versa; nothing in the endpoint network can connect to the caller.

Endpoints are a fundamentally stronger security model because you don't need to use routes, security groups, and ACLs to configure access. Endpoints also involve less configuration.

From a cost standpoint, VPC peering is cheaper. You're charged $0.01/GB in both directions when the traffic is cross-AZ. Traffic over a peering connection within the same AZ is free. With endpoints, you're charged an hourly rate for each VPC endpoint, plus $0.01/GB in both directions plus the same cross-AZ data transfer rates.

profile picture
answered 4 days ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions