1 Answers
0
Hello,
Endpoint services are available in the AWS Region in which they are created and can be accessed in remote AWS Regions using Inter-Region VPC Peering.
The flow would look like this:
Consumer VPC (Region A) ---PrivateLink---> NLB in Provider VPC (Region A) <---Inter-Region VPC Peering---> Endpoints in Provider VPC (Region B)
See the 'Inter-Region Endpoint Services' pattern - https://d1.awsstatic.com/whitepapers/aws-privatelink.pdf
Also see this: https://aws.amazon.com/about-aws/whats-new/2018/10/aws-privatelink-now-supports-access-over-inter-region-vpc-peering/
answered a month ago
Relevant questions
Cross-Account // Cross Org costs
asked 3 months agoDoes CodeBuild support cross-account access with CodeCommit?
Accepted Answerasked 3 years agoSQS interface endpoint for cross region access
Accepted Answerasked 2 years agoDynamoDB replication cross region
Accepted Answerasked 4 years agoAmazon Aurora cross-account and cross-region backup
asked 6 months agoCross-account cross-region in cloudwatch for specific log group
asked 8 months agoCloudWatch metrics and alarms Cross-account/Cross-Region with CloudFormation
asked 3 months agoCross Region private link
Accepted Answerasked 6 months agoQuerying Athena Iceberg Tables Cross Account
asked 3 months agoPrivate Link cross region cross account support
asked a month ago
So if I have an Account A (region -A ) and I have account B (region B) then this will not work?
I was able to create Account A (region -A ) and I have account B (region A) and private link works fine.
Hi, That should work also (see this - https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/peer-with-vpc-in-another-account.html) If you found the answer useful please accept the answer. Thank you.