AWS Security ChangesHomeSearch

AWS athena high security documentation change

Service: athena · 2025-08-16 · Security-related high

File: athena/latest/ug/connectors-vertica.md

Summary

Added parameters for Glue connections, casing modes, and security requirements. Removed spill parameters section. Updated connection string formatting.

Security assessment

Explicitly states that credentials must be stored in AWS Secrets Manager and enforces ConnectionSchemaVersion 2 compliance. These changes directly address credential management security practices.

Diff

diff --git a/athena/latest/ug/connectors-vertica.md b/athena/latest/ug/connectors-vertica.md
index 652606ae7..ef0c95a3d 100644
--- a//athena/latest/ug/connectors-vertica.md
+++ b//athena/latest/ug/connectors-vertica.md
@@ -5 +5 @@
-PrerequisitesLimitationsWorkflowTermsParametersConnection stringSpill parametersData type supportPerformancePassthrough queriesLicense informationAdditional resources
+PrerequisitesLimitationsWorkflowTermsParametersData type supportPerformancePassthrough queriesLicense informationAdditional resources
@@ -94,0 +95,37 @@ The following terms relate to the Vertica connector.
+Use the parameters in this section to configure the Vertica connector.
+
+We recommend that you configure a Vertica connector by using a Glue connections object. To do this, set the `glue_connection` environment variable of the Vertica connector Lambda to the name of the Glue connection to use.
+
+**Glue connections properties**
+
+Use the following command to get the schema for a Glue connection object. This schema contains all the parameters that you can use to control your connection.
+    
+    
+    aws glue describe-connection-type --connection-type VERTICA
+
+**Lambda environment properties**
+
+  * glue_connection – Specifies the name of the Glue connection associated with the federated connector. 
+
+  * **casing_mode** – (Optional) Specifies how to handle casing for schema and table names. The `casing_mode` parameter uses the following values to specify the behavior of casing:
+
+    * **none** – Do not change case of the given schema and table names. This is the default for connectors that have an associated glue connection. 
+
+    * **upper** – Upper case all given schema and table names.
+
+    * **lower** – Lower case all given schema and table names.
+
+
+
+
+###### Note
+
+  * All connectors that use Glue connections must use AWS Secrets Manager to store credentials.
+
+  * The Vertica connector created using Glue connections does not support the use of a multiplexing handler.
+
+  * The Vertica connector created using Glue connections only supports `ConnectionSchemaVersion` 2.
+
+
+
+
@@ -118 +155 @@ The Amazon Athena Vertica connector exposes configuration options through Lambda
-## Connection string
+#### Connection string
@@ -123 +160,3 @@ Use a JDBC connection string in the following format to connect to a database in
-    vertica://jdbc:vertica://host_name:port/database?user=vertica-username&password=vertica-password
+    vertica://jdbc:vertica://host_name:
+                            port/database?user=vertica-username&password=
+                            vertica-password
@@ -125 +164,2 @@ Use a JDBC connection string in the following format to connect to a database in
-### Using a single connection handler
+
+#### Using a single connection handler 
@@ -135 +175 @@ Record handler | `VerticaRecordHandler`
-### Single connection handler parameters
+#### Single connection handler parameters 
@@ -143 +183 @@ The single connection handlers support one database instance and must provide a
-### Providing credentials
+#### Providing credentials 
@@ -169 +209,3 @@ The following string has the secret names ${`vertica-username`} and `${vertica-p
-    vertica://jdbc:vertica://host_name:port/database?user=${vertica-username}&password=${vertica-password}
+    vertica://jdbc:vertica://
+                            host_name:port/database?user=${vertica-username}&password=${vertica-password}
+                        
@@ -174 +216,3 @@ The connector uses the secret name to retrieve secrets and provide the user name
-    vertica://jdbc:vertica://host_name:port/database?user=sample-user&password=sample-password
+    vertica://jdbc:vertica://
+                            host_name:port/database?user=sample-user&password=sample-password
+                        
@@ -178 +222 @@ Currently, the Vertica connector recognizes the `vertica-username` and `vertica-
-## Spill parameters
+#### Spill parameters