AWS Security ChangesHomeSearch

AWS athena documentation change

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

File: athena/latest/ug/connectors-azure-synapse.md

Summary

Fixed apostrophe in security warning and maintained security best practice recommendation

Security assessment

Same as other Athena connector files - maintains existing security documentation quality without addressing new vulnerabilities.

Diff

diff --git a/athena/latest/ug/connectors-azure-synapse.md b/athena/latest/ug/connectors-azure-synapse.md
index b91cc190a..9e0e110e0 100644
--- a//athena/latest/ug/connectors-azure-synapse.md
+++ b//athena/latest/ug/connectors-azure-synapse.md
@@ -112 +112 @@ 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_.