AWS Security ChangesHomeSearch

AWS redshift medium security documentation change

Service: redshift · 2025-05-10 · Security-related medium

File: redshift/latest/dg/materialized-view-streaming-ingestion-getting-started-MSK.md

Summary

Corrected parameter name from 'ssm-secret-arn' to 'asm-secret-arn' in authentication syntax

Security assessment

Fixes incorrect reference to SSM (Systems Manager) instead of ASM (likely Secrets Manager). Using wrong secret manager could lead to credential misconfiguration.

Diff

diff --git a/redshift/latest/dg/materialized-view-streaming-ingestion-getting-started-MSK.md b/redshift/latest/dg/materialized-view-streaming-ingestion-getting-started-MSK.md
index 55614b741..b711246d8 100644
--- a//redshift/latest/dg/materialized-view-streaming-ingestion-getting-started-MSK.md
+++ b//redshift/latest/dg/materialized-view-streaming-ingestion-getting-started-MSK.md
@@ -184 +184 @@ Assuming you have an Apache Kafka cluster available, the first step is to define
-    [AUTHENTICATION_ARN 'acm-certificate-arn' | SECRET_ARN 'ssm-secret-arn' ];
+    {AUTHENTICATION_ARN 'acm-certificate-arn' |  SECRET_ARN 'asm-secret-arn'};
@@ -226 +226 @@ The following examples show how to set the broker URI for the Amazon MSK cluster
-    AUTHENTICATION_ARN 'acm-certificate-arn' | [ SECRET_ARN 'ssm-secret-arn' ];
+    {AUTHENTICATION_ARN 'acm-certificate-arn' |  SECRET_ARN 'asm-secret-arn'}