AWS vpc-lattice documentation change
Summary
Clarified connection timeout parameters between VPC Lattice services and resources
Security assessment
Changes provide operational configuration details about connection timeouts but don't address security vulnerabilities or introduce security features
Diff
diff --git a/vpc-lattice/latest/ug/quotas.md b/vpc-lattice/latest/ug/quotas.md index 977c8816a..d0eef7268 100644 --- a//vpc-lattice/latest/ug/quotas.md +++ b//vpc-lattice/latest/ug/quotas.md @@ -45,2 +45,4 @@ Requests per second per service per Availability Zone | 10,000 | For HTTP servic -Connection idle time per connection | 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). -Maximum connection lifetime per connection | 10 minutes | The maximum time that a connection can be open. +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. +Maximum connection lifetime per connection for VPC Lattice services | 10 minutes | The maximum time that a connection can be open between the client and the server for VPC Lattice services. +Maximum connection lifetime per connection for VPC Lattice resources | NA | VPC Lattice doesn't impose any lifetime connection limits for resources. The client and the server determine the lifetime connection duration while being aware of the idle timeout for VPC Lattice resources, which is 350 seconds. +Connection idle time per connection for VPC Lattice resources | 350 seconds | You can use TCP keepalives to extend this idle timeout.