AWS athena documentation change
Summary
Added clarification about Lambda environment properties and updated terminology from 'Glue connections' to 'AWS Glue Data Catalog federated connection' in multiple sections
Security assessment
The changes are terminology updates and clarifications about when Lambda environment properties apply. The requirement to use AWS Secrets Manager was already present, and the change only clarifies the connection type. No evidence of addressing a specific security vulnerability.
Diff
diff --git a/athena/latest/ug/connectors-teradata.md b/athena/latest/ug/connectors-teradata.md index 584f1bd97..c3a57463f 100644 --- a//athena/latest/ug/connectors-teradata.md +++ b//athena/latest/ug/connectors-teradata.md @@ -72,0 +73,2 @@ Use the following command to get the schema for a Glue connection object. This s +The following Lambda environment properties apply only when you use the connector with a Lambda function in your account. + @@ -88 +90 @@ Use the following command to get the schema for a Glue connection object. This s - * All connectors that use Glue connections must use AWS Secrets Manager to store credentials. + * All connectors that use a AWS Glue Data Catalog federated connection must use AWS Secrets Manager to store credentials. @@ -90 +92 @@ Use the following command to get the schema for a Glue connection object. This s - * The Teradata connector created using Glue connections does not support the use of a multiplexing handler. + * The Teradata connector created using a AWS Glue Data Catalog federated connection does not support the use of a multiplexing handler. @@ -92 +94 @@ Use the following command to get the schema for a Glue connection object. This s - * The Teradata connector created using Glue connections only supports `ConnectionSchemaVersion` 2. + * The Teradata connector created using a AWS Glue Data Catalog federated connection only supports `ConnectionSchemaVersion` 2.