AWS Security ChangesHomeSearch

AWS sns documentation change

Service: sns · 2025-07-18 · Documentation low

File: sns/latest/dg/firehose-example-use-case.md

Summary

Updated architecture diagram caption and service name references

Security assessment

Service name standardization without security implications. Compliance references remain unchanged.

Diff

diff --git a/sns/latest/dg/firehose-example-use-case.md b/sns/latest/dg/firehose-example-use-case.md
index 885393a8f..b31539a10 100644
--- a//sns/latest/dg/firehose-example-use-case.md
+++ b//sns/latest/dg/firehose-example-use-case.md
@@ -13 +13 @@ The setting of this use case is an airline ticketing platform that operates in a
-  2. To meet the compliance goal on data retention, the company subscribes an Amazon Data Firehose delivery stream to an existing Amazon SNS topic.
+  2. To meet the compliance goal on data retention, the company subscribes an delivery stream to an existing Amazon SNS topic.
@@ -22 +22 @@ The following diagram shows the architecture of this configuration:
-![An AWS architecture for an airline ticketing platform, illustrating how ticket sales data is processed and archived. It shows the flow of data from a Lambda function through an Amazon SNS topic, which then distributes messages to Amazon SQS queues for payment processing and fraud detection, handled by respective Lambda functions. The data is also streamed via Amazon Kinesis Data Firehose to an Amazon S3 bucket for long-term archival, supporting compliance with data retention requirements. This setup enables the platform to run detailed analytics on ticket sales data using tools like Amazon Athena.](/images/sns/latest/dg/images/sns-archiving-use-case.png)
+![An AWS architecture for an airline ticketing platform, illustrating how ticket sales data is processed and archived. It shows the flow of data from a Lambda function through an Amazon SNS topic, which then distributes messages to Amazon SQS queues for payment processing and fraud detection, handled by respective Lambda functions. The data is also streamed via Data Firehose to an Amazon S3 bucket for long-term archival, supporting compliance with data retention requirements. This setup enables the platform to run detailed analytics on ticket sales data using tools like Amazon Athena.](/images/sns/latest/dg/images/sns-archiving-use-case.png)