Skip to content

Commit 720963f

Browse files
committed
add note about AZ availability and cross-region connections
1 parent 378619b commit 720963f

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

deploy-manage/security/private-connectivity-aws.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -135,6 +135,10 @@ $ aws ec2 describe-availability-zones --region us-east-1 | jq -c '.AvailabilityZ
135135

136136
The mapping will be different for your region. Our production VPC Service for `us-east-1` is located in `use1-az2`, `use1-az4`, `use1-az6`. We need to create the VPC Endpoint for the preceding mapping in at least one of `us-east-1e`, `us-east-1a`, `us-east-1b`.
137137

138+
:::{note}
139+
This limitation does not apply to [cross-region PrivateLink connections](#ec-aws-inter-region-private-link). If you're creating a cross-region connection, then you don't need to check that your VPC is present in all availability zones.
140+
:::
141+
138142
### Create your VPC endpoint and DNS entries in AWS [ec-aws-vpc-dns]
139143

140144
1. Create a VPC endpoint in your VPC using the service name for your region.

0 commit comments

Comments
 (0)