AWS Security ChangesHomeSearch

AWS athena documentation change

Service: athena · 2025-05-25 · Documentation low

File: athena/latest/ug/connectors-cloudera-impala.md

Summary

Fixed apostrophe in security warning and maintained security best practice recommendation

Security assessment

Grammatical correction in existing security advice. No new security content added beyond maintaining existing guidance.

Diff

diff --git a/athena/latest/ug/connectors-cloudera-impala.md b/athena/latest/ug/connectors-cloudera-impala.md
index 9d416e266..e0ceb8da3 100644
--- a//athena/latest/ug/connectors-cloudera-impala.md
+++ b//athena/latest/ug/connectors-cloudera-impala.md
@@ -102 +102 @@ To provide a user name and password for your database in your JDBC connection st
-As a security best practice, don&t use hardcoded credentials in your environment variables or connection strings. For information about moving your hardcoded secrets to AWS Secrets Manager, see [Move hardcoded secrets to AWS Secrets Manager](https://docs.aws.amazon.com/secretsmanager/latest/userguide/hardcoded.html) in the _AWS Secrets Manager User Guide_.
+As a security best practice, don't use hardcoded credentials in your environment variables or connection strings. For information about moving your hardcoded secrets to AWS Secrets Manager, see [Move hardcoded secrets to AWS Secrets Manager](https://docs.aws.amazon.com/secretsmanager/latest/userguide/hardcoded.html) in the _AWS Secrets Manager User Guide_.