2 ms·
AWS PrivateLink has another property that generally makes it undesirable for these types of integrations: communication is bidirectional, and IP subnets should
by stingraycharles 3y ago
AWS PrivateLink has another property that generally makes it undesirable for these types of integrations: communication is bidirectional, and IP subnets should not overlap.
We (as a vendor ourselves) typically integrate as a VPC Endpoint Service, where communication is unidirectional and our service is exposed as a load balancer’s endpoint within the customer’s VPC.
- EE84M3i 3y agoI thought PrivateLink was branding for vpc interface endpoints? There's no ip subject restriction for that because it's basically a proxy. Are you thinking of vpc peering? VPC endpoints seem preferable in this situation.
- stingraycharles 3y agoOh I apologize, you’re completely correct and I am confusing PrivateLink with VPC peering. Thank you for correcting me.