AWS AmazonCloudWatch documentation change
Summary
Updated product name references from 'Kinesis Data Streams' to 'Amazon Kinesis Data Streams' for branding consistency
Security assessment
Changes involve branding/naming updates only. No security implications identified as the modifications don't alter security controls, permissions, or vulnerability guidance.
Diff
diff --git a/AmazonCloudWatch/latest/logs/CrossAccountSubscriptions.md b/AmazonCloudWatch/latest/logs/CrossAccountSubscriptions.md index 777ba59bc..0cef541ef 100644 --- a//AmazonCloudWatch/latest/logs/CrossAccountSubscriptions.md +++ b//AmazonCloudWatch/latest/logs/CrossAccountSubscriptions.md @@ -7 +7 @@ -You can collaborate with an owner of a different AWS account and receive their log events on your AWS resources, such as an Amazon Kinesis or Amazon Data Firehose stream (this is known as cross-account data sharing). For example, this log event data can be read from a centralized Kinesis Data Streams or Firehose stream to perform custom processing and analysis. Custom processing is especially useful when you collaborate and analyze data across many accounts. +You can collaborate with an owner of a different AWS account and receive their log events on your AWS resources, such as an Amazon Kinesis or Amazon Data Firehose stream (this is known as cross-account data sharing). For example, this log event data can be read from a centralized Amazon Kinesis Data Streams or Firehose stream to perform custom processing and analysis. Custom processing is especially useful when you collaborate and analyze data across many accounts. @@ -9 +9 @@ You can collaborate with an owner of a different AWS account and receive their l -For example, a company's information security group might want to analyze data for real-time intrusion detection or anomalous behaviors so it could conduct an audit of accounts in all divisions in the company by collecting their federated production logs for central processing. A real-time stream of event data across those accounts can be assembled and delivered to the information security groups, who can use Kinesis Data Streams to attach the data to their existing security analytic systems. +For example, a company's information security group might want to analyze data for real-time intrusion detection or anomalous behaviors so it could conduct an audit of accounts in all divisions in the company by collecting their federated production logs for central processing. A real-time stream of event data across those accounts can be assembled and delivered to the information security groups, who can use Amazon Kinesis Data Streams to attach the data to their existing security analytic systems. @@ -30 +30 @@ These dimensions help in identifying the source of log data, allowing for more g - * [Cross-account cross-Region log data sharing using Kinesis Data Streams](./CrossAccountSubscriptions-Kinesis.html) + * [Cross-account cross-Region log data sharing using Amazon Kinesis Data Streams](./CrossAccountSubscriptions-Kinesis.html) @@ -34 +34 @@ These dimensions help in identifying the source of log data, allowing for more g - * [Cross-account cross-Region account-level subscriptions using Kinesis Data Streams](./CrossAccountSubscriptions-Kinesis-Account.html) + * [Cross-account cross-Region account-level subscriptions using Amazon Kinesis Data Streams](./CrossAccountSubscriptions-Kinesis-Account.html) @@ -49 +49 @@ Account-level subscription filters -Cross-account cross-Region log data sharing using Kinesis Data Streams +Cross-account cross-Region log data sharing using Amazon Kinesis Data Streams