AWS Security ChangesHomeSearch

AWS redshift: ODBC driver SSLMode default changed to verify-full and logging simplified

Service: redshift · 2026-10-21 · Documentation medium

File: redshift/latest/mgmt/odbc20-configuration-options.md · Type: encryption

Summary

Documents that the default SSLMode is now verify-full (was verify-ca) starting in driver 2.3.0, and that the separate handshake log file is deprecated in favor of a single log file.

Security assessment

Changing the default SSL mode from verify-ca to verify-full strengthens TLS hostname verification, reducing man-in-the-middle risk; this is security-hardening documentation rather than a fix for a specific vulnerability.

Evidence

+  * Default Value – `verify-full`

Diff

diff --git a/redshift/latest/mgmt/odbc20-configuration-options.md b/redshift/latest/mgmt/odbc20-configuration-options.md
index 8538a2d..7468ace 100644
--- a//redshift/latest/mgmt/odbc20-configuration-options.md
+++ b//redshift/latest/mgmt/odbc20-configuration-options.md
@@ -937,7 +937 @@ Log level 5 (DEBUG) or higher captures all driver activity, which may include se
-When logging is enabled, the driver produces the following log files at the location you specify in the **LogPath** property: 
-
-  * A `redshift_odbc.log.1` file that logs driver activity that takes place during handshake of a connection. 
-
-  * A `redshift_odbc.log` file for all driver activities after a connection is made to the database. 
-
-
+When you enable logging, the driver writes all driver activity to a `redshift_odbc.log` file in the location that you specify in the **LogPath** property.
@@ -944,0 +939 @@ When logging is enabled, the driver produces the following log files at the loca
+Starting with driver version 2.3.0, the separate `redshift_odbc.log.1` connection handshake log is deprecated, and the driver no longer creates it.
@@ -1347 +1342 @@ This parameter is optional.
-  * Default Value – `verify-ca`
+  * Default Value – `verify-full`
@@ -1374,0 +1370,2 @@ We recommend using `verify-full` for SSL connections whenever possible.
+In driver versions 2.3.0 and later, the default is `verify-full`. In earlier versions, the default was `verify-ca`. If you don't set `SSLMode` and the server certificate doesn't match the host name, the driver logs a warning and connects. If you set `SSLMode`, the driver enforces the mode that you set.
+