AWS redshift medium security documentation change
Summary
Clarified that TLS version enforcement only affects clusters using TLS
Security assessment
The change explicitly documents security controls around TLS version requirements, helping users understand encryption compliance needs. This addresses secure communication configuration.
Diff
diff --git a/redshift/latest/mgmt/behavior-changes.md b/redshift/latest/mgmt/behavior-changes.md index b44ad883e..08c8396c4 100644 --- a//redshift/latest/mgmt/behavior-changes.md +++ b//redshift/latest/mgmt/behavior-changes.md @@ -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. +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.