Cross Region private link
I'd like to be able to configure private link across regions as a provider only supports it's product in a region they we don't have our workloads in. Currently this is not available ( Feb 2022 ). Is the current best practice to setup the private link in the same region as the provider then use VPC peering to connect back to my application in the "other region"?
- Language
- English
- Newest
- Most votes
- Most comments
Basis for the pattern is from this whitepaper - https://d1.awsstatic.com/whitepapers/aws-privatelink.pdf
Deploy a dedicated VPC in vendor region in your account
Create a Private Link connection between Vendor account and your account
Create a cross region VPC peering connection between your VPCs
Hey AWS-User-1585900 - typically if you are interacting with a 3rd party provider you want to use Private Link and not use something like a transit gateway. Connecting all of your own VPCs together across regions, transit gateway peering would be perfect.
You can now leverage AWS PrivateLink native cross-region connectivity. it will enable you to connect to VPC endpoint services hosted in other AWS Regions in the same AWS partition over Interface endpoints.
https://aws.amazon.com/about-aws/whats-new/2024/11/aws-privatelink-across-region-connectivity/
As of November 2024 cross-region PrivateLink is supported for customer VPC Endpoint services: https://aws.amazon.com/about-aws/whats-new/2024/11/aws-privatelink-across-region-connectivity/
Relevant content
- asked 3 years ago
- asked 2 years ago
Thanks for that reference and for confirming AJ.
will it work with Transit Gateway connection between regions instead of cross region VPC peering ?
Yes, it will. However, note that as of November 2024 cross-region PrivateLink is supported for customer VPC Endpoint services: https://aws.amazon.com/about-aws/whats-new/2024/11/aws-privatelink-across-region-connectivity/