AWS Security ChangesHomeSearch

AWS solutions documentation change

Service: solutions · 2025-03-02 · Documentation low

File: solutions/latest/scalable-analytics-using-apache-druid-on-aws/metadata-storage.md

Summary

Minor punctuation change in the description of database credentials storage

Security assessment

The change only involves a punctuation mark update (apostrophe style) in existing security documentation, without adding new security information or addressing a specific security issue.

Diff

diff --git a/solutions/latest/scalable-analytics-using-apache-druid-on-aws/metadata-storage.md
index c2e0099f3..b0471a3cd 100644
--- a/solutions/latest/scalable-analytics-using-apache-druid-on-aws/metadata-storage.md
+++ b/solutions/latest/scalable-analytics-using-apache-druid-on-aws/metadata-storage.md
@@ -7 +7 @@
-By default, the solution deploys an Amazon Aurora PostgreSQL cluster in an isolated subnet to serve as metadata storage for the Druid cluster, ensuring TLS connectivity to secure communication with the DB cluster. It also generates a secret to store the credentials of the DB cluster's master user. For example, for credentials for the master user of Amazon Aurora cluster.
+By default, the solution deploys an Amazon Aurora PostgreSQL cluster in an isolated subnet to serve as metadata storage for the Druid cluster, ensuring TLS connectivity to secure communication with the DB cluster. It also generates a secret to store the credentials of the DB cluster’s master user. For example, for credentials for the master user of Amazon Aurora cluster.