AWS Security ChangesHomeSearch

AWS athena documentation change

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

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

Summary

Fixed typo in security advice: replaced 'don&t' with 'don't' in the recommendation to avoid hardcoded credentials

Security assessment

Typo correction in pre-existing security documentation. Does not indicate a security issue resolution or new security feature addition.

Diff

diff --git a/athena/latest/ug/connectors-postgresql.md b/athena/latest/ug/connectors-postgresql.md
index fa0866f1b..a1c754d0c 100644
--- a//athena/latest/ug/connectors-postgresql.md
+++ b//athena/latest/ug/connectors-postgresql.md
@@ -123 +123 @@ 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_.