AWS Security ChangesHomeSearch

AWS firehose documentation change

Service: firehose · 2025-06-25 · Documentation low

File: firehose/latest/dev/controlling-access.md

Summary

Added multiple JSON formatting blocks and section dividers (****) throughout IAM policy examples

Security assessment

Formatting improvements to existing IAM policy examples. No changes to security-related content or policies.

Diff

diff --git a/firehose/latest/dev/controlling-access.md b/firehose/latest/dev/controlling-access.md
index 5388ffa8b..a59dc4bb2 100644
--- a//firehose/latest/dev/controlling-access.md
+++ b//firehose/latest/dev/controlling-access.md
@@ -65,0 +66,6 @@ To give your application access to your Firehose stream, use a policy similar to
+JSON
+    
+
+****
+    
+    
@@ -88,0 +96,6 @@ If the source of your Firehose stream is a private Amazon MSK cluster, then use
+JSON
+    
+
+****
+    
+    
@@ -134,0 +149,6 @@ If you choose Amazon MSK as the source for your Firehose stream, you must specif
+JSON
+    
+
+****
+    
+    
@@ -153,0 +175,6 @@ Make sure that this role that grants Amazon Data Firehose permissions to ingest
+JSON
+    
+
+****
+    
+    
@@ -208,0 +237,6 @@ Use the following access policy to enable Amazon Data Firehose to access your S3
+JSON
+    
+
+****
+    
+    
@@ -323,0 +359,6 @@ Create a policy and choose **JSON** in the policy editor. Add the following inli
+JSON
+    
+
+****
+    
+    
@@ -441,0 +484,6 @@ You must have an IAM role before you create a Firehose stream and Apache Iceberg
+JSON
+    
+
+****
+    
+    
@@ -562,0 +612,6 @@ Use the following access policy to enable Amazon Data Firehose to access your S3
+JSON
+    
+
+****
+    
+    
@@ -686,0 +743,6 @@ Use the following access policy to enable Amazon Data Firehose to access your S3
+JSON
+    
+
+****
+    
+    
@@ -829,0 +893,6 @@ Use the following access policy to enable Amazon Data Firehose to access your S3
+JSON
+    
+
+****
+    
+    
@@ -972,0 +1043,6 @@ Use the following access policy to enable Amazon Data Firehose to access your S3
+JSON
+    
+
+****
+    
+    
@@ -1107,0 +1185,6 @@ You must have an IAM role before you create a Firehose stream. Firehose assumes
+JSON
+    
+
+****
+    
+    
@@ -1205,0 +1290,6 @@ Amazon Data Firehose doesn't use IAM to access HTTP endpoint destinations owned
+JSON
+    
+
+****
+    
+    
@@ -1408,0 +1500,6 @@ The Amazon S3 bucket specified in the access policy is owned by account B in thi
+JSON
+    
+
+****
+    
+    
@@ -1450,0 +1549,6 @@ You can use the AWS CLI or the Amazon Data Firehose APIs to create a Firehose st
+JSON
+    
+
+****
+    
+    
@@ -1491,0 +1597,6 @@ For the `CreateDeliveryStream` operation, use the `aws:RequestTag` condition key
+JSON
+    
+
+****
+    
+    
@@ -1513,0 +1626,6 @@ For the `TagDeliveryStream` operation, use the `aws:TagKeys` condition key. In t
+JSON
+    
+
+****
+    
+    
@@ -1534,0 +1654,6 @@ For the `UntagDeliveryStream` operation, use the `aws:TagKeys` condition key. In
+JSON
+    
+
+****
+    
+    
@@ -1563,0 +1690,6 @@ In the following example, `MyKey` and `MyValue` represent the key and correspond
+JSON
+    
+
+****
+    
+