AWS redshift documentation change
Summary
Updated enforcement date for minimum TLS version 1.2 requirement from January 31, 2026 to July 30, 2026.
Security assessment
This documents a future security enhancement (TLS 1.2 enforcement) but only changes the timeline. No new vulnerability is addressed; it maintains existing security documentation about phasing out weak TLS versions.
Diff
diff --git a/redshift/latest/mgmt/behavior-changes.md b/redshift/latest/mgmt/behavior-changes.md index b806ebbd8..31666b85e 100644 --- a//redshift/latest/mgmt/behavior-changes.md +++ b//redshift/latest/mgmt/behavior-changes.md @@ -35 +35 @@ The following describes upcoming behavior changes. - * Minimum Transport Layer Security (TLS) version changes effective starting January 31, 2026 + * Minimum Transport Layer Security (TLS) version changes effective starting July 30, 2026 @@ -134 +134 @@ Starting February 16, 2026, Amazon Redshift will no longer support the usage of -### Minimum Transport Layer Security (TLS) version changes effective starting January 31, 2026 +### Minimum Transport Layer Security (TLS) version changes effective starting July 30, 2026 @@ -136 +136 @@ Starting February 16, 2026, Amazon Redshift will no longer support the usage of -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. +Beginning July 30, 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.