AWS vpc documentation change
Summary
Reorganized content and added detailed considerations section for resource gateways
Security assessment
The changes are organizational and add general operational considerations, but do not address security vulnerabilities or introduce new security features.
Diff
diff --git a/vpc/latest/privatelink/resource-gateway.md index b4cc1061b..05f912ff7 100644 --- a/vpc/latest/privatelink/resource-gateway.md +++ b/vpc/latest/privatelink/resource-gateway.md @@ -5 +5 @@ -Security groupsIP address types +ConsiderationsSecurity groupsIP address types @@ -9 +9 @@ Security groupsIP address types -A resource gateway is a point of inbound traffic into the VPC where a resource resides. For your resource to be accessible from all Availability Zones, you should create your resource gateways to span as many Availability Zones as possible. At least one Availability Zone of the VPC endpoint and the resource gateway have to overlap. +A resource gateway is a point of inbound traffic into the VPC where a resource resides. It spans multiple Availability Zones. @@ -16,0 +17,2 @@ A resource gateway does not provide load balancing capabilities. + * Considerations + @@ -27,0 +30,15 @@ A resource gateway does not provide load balancing capabilities. +## Considerations + +The following considerations apply to resource gateways: + + * For your resource to be accessible from all [Availability Zones](https://aws.amazon.com/about-aws/global-infrastructure/regions_az/), you should create your resource gateways to span as many Availability Zones as possible. + + * At least one Availability Zone of the VPC endpoint and the resource gateway have to overlap. + + * A VPC can have a maximum of 100 resource gateways. For more information, see [Quotas for VPC Lattice](https://docs.aws.amazon.com/vpc-lattice/latest/ug/quotas.html). + + * You can't create a resource gateway in a shared subnet. + + + +