AWS athena documentation change
Summary
Added documentation for configuring HBase connector via Glue connections, including mandatory use of AWS Secrets Manager for credentials and connection schema version constraints.
Security assessment
The change mandates AWS Secrets Manager for credential storage (security best practice) but does not address a specific vulnerability. It improves security documentation rather than fixing an existing issue.
Diff
diff --git a/athena/latest/ug/connectors-hbase.md b/athena/latest/ug/connectors-hbase.md index 5b8ba6123..b0a1a1c0e 100644 --- a//athena/latest/ug/connectors-hbase.md +++ b//athena/latest/ug/connectors-hbase.md @@ -39,0 +40,27 @@ The parameter names and definitions listed below are for Athena data source conn +We recommend that you configure a HBase connector by using a Glue connections object. To do this, set the `glue_connection` environment variable of the HBase 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 HBASE + +**Lambda environment properties** + + * glue_connection – Specifies the name of the Glue connection associated with the federated connector. + + + + +###### Note + + * All connectors that use Glue connections must use AWS Secrets Manager to store credentials. + + * The HBase connector created using Glue connections does not support the use of a multiplexing handler. + + * The HBase connector created using Glue connections only supports `ConnectionSchemaVersion` 2. + + + + @@ -61 +88 @@ The parameter names and definitions listed below are for Athena data source conn -### Specifying connection strings +#### Specifying connection strings @@ -76 +103 @@ Before you can use these two SQL statements, you must add two environment variab -#### Using secrets +##### Using secrets