Inter-Region access to endpoint services
Dear Team - As per last use case Inter-Region access to endpoint services description in https://docs.aws.amazon.com/whitepapers/latest/aws-privatelink/use-case-examples.html, the ENI of interface endpoint circled in red should not be in Consumer VPC of remote region ?
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
VPCs are regional constructs, and so are VPC endpoints. A VPC endpoint can only be created in the same region where the resource used to deliver it (NLB in this case) resides. Even more specifically for VPC interface endpoints, the ENIs of the endpoint must each reside in the same availability zone as one of the ENIs of one of the NLBs used to provide the VPC endpoint service.
You can, however, access a VPC interface endpoint in a remote region over an inter-region VPC peering connection (or several other means), and that's the scenario illustrated in the diagram.
Note that starting Nov 26 2024 cross-region PrivateLink is now supported.
https://aws.amazon.com/about-aws/whats-new/2024/11/aws-privatelink-across-region-connectivity/
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 3 Jahren
Hi, Please note that with the release of cross-region PrivateLink in Nov 2024, this answer is no longer correct. Thank you!