AWS redshift documentation change
Summary
Updated TLS 1.2 enforcement date and terminology (clusters → data warehouses)
Security assessment
The change adjusts the timeline for a previously announced security control (TLS 1.2 enforcement) but does not introduce new security documentation or address an active vulnerability.
Diff
diff --git a/redshift/latest/mgmt/behavior-changes.md b/redshift/latest/mgmt/behavior-changes.md index 08c8396c4..41bb4c840 100644 --- a//redshift/latest/mgmt/behavior-changes.md +++ b//redshift/latest/mgmt/behavior-changes.md @@ -23 +23 @@ The following describes upcoming behavior changes. - * Minimum Transport Layer Security (TLS) version changes effective after October 31, 2025 + * Minimum Transport Layer Security (TLS) version changes effective starting January 31, 2026 @@ -53 +53 @@ Starting February 16, 2026, Amazon Redshift will no longer support the usage of -### Minimum Transport Layer Security (TLS) version changes effective after October 31, 2025 +### Minimum Transport Layer Security (TLS) version changes effective starting January 31, 2026 @@ -55 +55 @@ Starting February 16, 2026, Amazon Redshift will no longer support the usage of -Beginning October 31, 2025, Amazon Redshift will enforce a minimum Transport Layer Security (TLS) version of 1.2. Incoming connections that use TLS versions 1.0 or 1.1 will be rejected. This applies to both Amazon Redshift provisioned clusters and serverless workgroups. Amazon Redshift clusters not using TLS will not be affected by this change. +Beginning January 31, 2026, Amazon Redshift will enforce a minimum Transport Layer Security (TLS) version of 1.2. Incoming connections that use TLS versions 1.0 or 1.1 will be rejected. This applies to both Amazon Redshift provisioned clusters and serverless workgroups. Amazon Redshift data warehouses not using TLS will not be affected by this change.