AWS vpc-lattice documentation change
Summary
Made connection idle time configurable (60-600 seconds) with API parameters
Security assessment
Configuration change for connection management without security implications. No mention of vulnerabilities, attacks, or security controls. Routine feature enhancement documentation.
Diff
diff --git a/vpc-lattice/latest/ug/quotas.md b/vpc-lattice/latest/ug/quotas.md index da2996aad..88c70631b 100644 --- a//vpc-lattice/latest/ug/quotas.md +++ b//vpc-lattice/latest/ug/quotas.md @@ -50 +50 @@ Requests per second per service per Availability Zone | 10,000 | For HTTP servic -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. +Connection idle time per connection for VPC Lattice services | Configurable with a default of 60 seconds (range: 60–600 seconds) | The time that a connection can sit idle with no active requests (for HTTP and gRPC), or with no active data transfer (for TLS passthrough). You can configure this value per service using the `idleTimeoutSeconds` parameter in the [CreateService](https://docs.aws.amazon.com/vpc-lattice/latest/APIReference/API_CreateService.html) or [UpdateService](https://docs.aws.amazon.com/vpc-lattice/latest/APIReference/API_UpdateService.html) API. You can also use HTTP and application-level keepalives to keep connections alive up to the maximum connection lifetime of 10 minutes.