AWS AmazonElastiCache: Require transit encryption mode 'required' for AUTH and HIPAA
Summary
Clarifies in the authentication docs that in-transit encryption (TLS) must be set to mode 'required' (not just enabled) for AUTH token usage and HIPAA eligibility, including for token rotation and for enabling authentication on existing clusters; also updates the sample CLI description.
Security assessment
The added line strengthens documented security posture by requiring TLS mode 'required' for AUTH token authentication and HIPAA eligibility, directly tied to encryption-in-transit and authentication configuration, but it is guidance rather than a fix for a disclosed vulnerability.
Evidence
+ * `--transit-encryption-mode` – Must be `required` or omitted for authentication and HIPAA eligibility.
Diff
diff --git a/AmazonElastiCache/latest/dg/auth.md b/AmazonElastiCache/latest/dg/auth.md index 0c6a47d..f958f88 100644 --- a//AmazonElastiCache/latest/dg/auth.md +++ b//AmazonElastiCache/latest/dg/auth.md @@ -68 +68 @@ You can require that users enter a token (password) on a token-protected Valkey -The following AWS CLI operation creates a replication group with encryption in transit (TLS) enabled and the **AUTH** token ``This-is-a-sample-token``. Replace the subnet group `sng-test` with a subnet group that exists. +The following AWS CLI operation creates a replication group that has encryption in transit (TLS) enabled and required, with the **AUTH** token ``This-is-a-sample-token``. Replace the subnet group `sng-test` with a subnet group that exists. @@ -77,0 +78,2 @@ The following AWS CLI operation creates a replication group with encryption in t + * `--transit-encryption-mode` – Must be `required` or omitted for authentication and HIPAA eligibility. + @@ -115 +117 @@ For Windows: -To make it easier to update your authentication, you can modify the **AUTH** token used on a cluster. You can make this modification if the engine version is Valkey 7.2 or higher or Redis 5.0.6 or higher. ElastiCache must also have encryption in transit enabled. For more information, see [ElastiCache in-transit encryption (TLS)](./in-transit-encryption.html). +To make it easier to update your authentication, you can modify the **AUTH** token used on a cluster. You can make this modification if the engine version is Valkey 7.2 or higher or Redis 5.0.6 or higher. ElastiCache must also have encryption in transit enabled and transit encryption mode `required`. For more information, see [ElastiCache in-transit encryption (TLS)](./in-transit-encryption.html). @@ -183 +185 @@ To enable authentication on an existing Valkey or Redis OSS server, call the `Mo -After the ROTATE modification is complete, the cluster supports the **AUTH** token specified in the `--auth-token` parameter in addition to supporting connecting without authentication. Once all client applications are updated to authenticate to Valkey or Redis OSS with the AUTH token, use the SET strategy to mark the AUTH token as required. Enabling authentication is only supported on Valkey and Redis OSS servers with encryption in transit (TLS) enabled. +After the ROTATE modification is complete, the cluster supports the **AUTH** token specified in the `--auth-token` parameter in addition to supporting connecting without authentication. Once all client applications are updated to authenticate to Valkey or Redis OSS with the AUTH token, use the SET strategy to mark the AUTH token as required. Enabling authentication is only supported on Valkey and Redis OSS servers with encryption in transit (TLS) enabled and required.