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"?
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.
Relevant questions
SQS interface endpoint for cross region access
Accepted Answerasked 2 years agoPrivate Link cross region cross account support
asked a month agoCross Region private link
Accepted Answerasked 6 months agoOpen ID Connect Provider - create the identity provider in a specific region
asked 14 days agoCross-account cross-region in cloudwatch for specific log group
asked 8 months agoMove a IoT Thing to a different region
Accepted Answerasked 6 months agoHadoop across multiple regions
asked 3 years agoAmazon Connect outbound Caller ID set to private
asked a month agoLightsail: Resolve private hostnames
asked 4 months agoPrivate link access over direct connect - Direct Connect Gateway
Accepted Answerasked 4 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 ?