1 Answers
Thanks for sharing Arkadiusz! I just pushed an update to the slides. This is good news for those who use multiple regions and PrivateLink endpoints…before, they had to create them in each region.
Sign Up Free or Log In to participate!
Thanks for sharing Arkadiusz! I just pushed an update to the slides. This is good news for those who use multiple regions and PrivateLink endpoints…before, they had to create them in each region.
Psst…this one if you’ve been moved to ACG!
Why is there VPC Peeering needed for the PrivateLink? My understanding was that this is not necessary within the same region and also a better practice than peering as this is in line with the least priviledge principle.
If the PrivateLink endpoint only exists in one region, you can use VPC peering to privately connect to the service. You can read about it here: https://aws.amazon.com/about-aws/whats-new/2018/10/aws-privatelink-now-supports-access-over-inter-region-vpc-peering/
Thanks Scott, so it looks that across regions, you need peering between the VPC Endpoint Service and VPC Endpoint Interface to work. I expect this AWS will evolve this later on because within the same region, connection between the Service and the Interface works without extra the peering.