AWS vpc-lattice documentation change
Summary
Updated quota descriptions to clarify bandwidth and requests per second are default values that can be increased through support, and added contact guidance for quota increases
Security assessment
The changes focus on clarifying default values and quota adjustment processes rather than addressing security vulnerabilities or documenting security features. No security controls, vulnerabilities, or mitigations are mentioned in the changes.
Diff
diff --git a/vpc-lattice/latest/ug/quotas.md b/vpc-lattice/latest/ug/quotas.md index 77bf01755..ee7043bf4 100644 --- a//vpc-lattice/latest/ug/quotas.md +++ b//vpc-lattice/latest/ug/quotas.md @@ -41 +41 @@ Limit | Value | Description -Bandwidth per service per Availability Zone | 10 Gbps | The maximum bandwidth allocated per service per Availability Zone. +Bandwidth per service per Availability Zone | 10 Gbps | The default bandwidth allocated per service per Availability Zone. This can be increased, contact your Solutions Architect (SA) or Technical Account Manager (TAM) for further assistance. @@ -43,2 +43,2 @@ Maximum transmission unit (MTU) per connection | 8500 bytes | The size of the la -Requests per second per service per Availability Zone | 10,000 | For HTTP services, this is the maximum number of requests per second per service per Availability Zone. -Connection idle time per connection for VPC Lattice services | 1 minute | The maximum time that a connection can sit idle with no active requests (for HTTP and GRPC), or with no active data transfer (for TLS-PASSTHROUGH) for VPC Lattice services. You can use HTTP and application-level keepalives to extend this idle timeout up to the maximum connection lifetime duration. +Requests per second per service per Availability Zone | 10,000 | For HTTP services, this is the default number of requests per second per service per Availability Zone. This can be increased, contact your Solutions Architect (SA) or Technical Account Manager (TAM) for further assistance. +Connection idle time per connection for VPC Lattice services | 1 minute | The default time that a connection can sit idle with no active requests (for HTTP and GRPC), or with no active data transfer (for TLS-PASSTHROUGH) for VPC Lattice services. You can use HTTP and application-level keepalives to extend this idle timeout up to the maximum connection lifetime duration. This can be increased, contact your Solutions Architect (SA) or Technical Account Manager (TAM) for further assistance.