AWS AmazonCloudWatch documentation change
Summary
Updated service name references from 'Kinesis Data Streams' to 'Amazon Kinesis Data Streams' throughout the document. Fixed a broken link in the Lambda section and made minor wording improvements.
Security assessment
The changes are purely cosmetic updates to service naming conventions and documentation links. No security vulnerabilities, configurations, or best practices were modified or added. The throttling mitigation advice remains unchanged and doesn't constitute new security documentation.
Diff
diff --git a/AmazonCloudWatch/latest/logs/SubscriptionFilters-AccountLevel.md b/AmazonCloudWatch/latest/logs/SubscriptionFilters-AccountLevel.md index b76ad05a3..7e4101eeb 100644 --- a//AmazonCloudWatch/latest/logs/SubscriptionFilters-AccountLevel.md +++ b//AmazonCloudWatch/latest/logs/SubscriptionFilters-AccountLevel.md @@ -5 +5 @@ -Example 1: Subscription filters with Kinesis Data StreamsExample 2: Subscription filters with AWS LambdaExample 3: Subscription filters with Amazon Data Firehose +Example 1: Subscription filters with Amazon Kinesis Data StreamsExample 2: Subscription filters with AWS LambdaExample 3: Subscription filters with Amazon Data Firehose @@ -13 +13 @@ There is a risk of causing an infinite recursive loop with subscription filters -You can set an account-level subscription policy that includes a subset of log groups in the account. The account subscription policy can work with Amazon Kinesis Data Streams, AWS Lambda, or Amazon Data Firehose. Logs sent to a service through an account-level subscription policy are base64 encoded and compressed with the gzip format. This section provides examples you can follow to create an account-level subscription for Kinesis Data Streams, Lambda, and Firehose. +You can set an account-level subscription policy that includes a subset of log groups in the account. The account subscription policy can work with Amazon Kinesis Data Streams, AWS Lambda, or Amazon Data Firehose. Logs sent to a service through an account-level subscription policy are base64 encoded and compressed with the gzip format. This section provides examples you can follow to create an account-level subscription for Amazon Kinesis Data Streams, Lambda, and Firehose. @@ -21 +21 @@ To view a list of all subscription filter policies in your account, use the `des - * Example 1: Subscription filters with Kinesis Data Streams + * Example 1: Subscription filters with Amazon Kinesis Data Streams @@ -30 +30 @@ To view a list of all subscription filter policies in your account, use the `des -## Example 1: Subscription filters with Kinesis Data Streams +## Example 1: Subscription filters with Amazon Kinesis Data Streams @@ -32 +32 @@ To view a list of all subscription filter policies in your account, use the `des -Before you create a Kinesis Data Streams data stream to use with an account-level subscription policy, calculate the volume of log data that will be generated. Be sure to create a stream with enough shards to handle this volume. If a stream doesn't have enough shards, it is throttled. For more information about stream volume limits, see [ Quotas and Limits](https://docs.aws.amazon.com/streams/latest/dev/service-sizes-and-limits.html) in the Kinesis Data Streams documentation. +Before you create a Amazon Kinesis Data Streams data stream to use with an account-level subscription policy, calculate the volume of log data that will be generated. Be sure to create a stream with enough shards to handle this volume. If a stream doesn't have enough shards, it is throttled. For more information about stream volume limits, see [ Quotas and Limits](https://docs.aws.amazon.com/streams/latest/dev/service-sizes-and-limits.html) in the Amazon Kinesis Data Streams documentation. @@ -40 +40 @@ To mitigate the risk of throttling, you can take the following steps: - * Monitor your Kinesis Data Streams stream with CloudWatch metrics. This helps you identify throttling and adjust your configuration accordingly. For example, the `DeliveryThrottling` metric tracks the number of log events for which CloudWatch Logs was throttled when forwarding data to the subscription destination. For more information, see [Monitoring with CloudWatch metrics](./CloudWatch-Logs-Monitoring-CloudWatch-Metrics.html). + * Monitor your Amazon Kinesis Data Streams stream with CloudWatch metrics. This helps you identify throttling and adjust your configuration accordingly. For example, the `DeliveryThrottling` metric tracks the number of log events for which CloudWatch Logs was throttled when forwarding data to the subscription destination. For more information, see [Monitoring with CloudWatch metrics](./CloudWatch-Logs-Monitoring-CloudWatch-Metrics.html). @@ -42 +42 @@ To mitigate the risk of throttling, you can take the following steps: - * Use the on-demand capacity mode for your stream in Kinesis Data Streams. On-demand mode instantly accommodates your workloads as they ramp up or down. For more information, see [ On-demand mode](https://docs.aws.amazon.com/streams/latest/dev/how-do-i-size-a-stream.html#ondemandmode). + * Use the on-demand capacity mode for your stream in Amazon Kinesis Data Streams. On-demand mode instantly accommodates your workloads as they ramp up or down. For more information, see [ On-demand mode](https://docs.aws.amazon.com/streams/latest/dev/how-do-i-size-a-stream.html#ondemandmode). @@ -44 +44 @@ To mitigate the risk of throttling, you can take the following steps: - * Restrict your CloudWatch Logs subscription filter pattern to match the capacity of your stream in Kinesis Data Streams. If you are sending too much data to the stream, you might need to reduce the filter size or adjust the filter criteria. + * Restrict your CloudWatch Logs subscription filter pattern to match the capacity of your stream in Amazon Kinesis Data Streams. If you are sending too much data to the stream, you might need to reduce the filter size or adjust the filter criteria. @@ -49 +49 @@ To mitigate the risk of throttling, you can take the following steps: -The following example uses an account-level subscription policy to forward all log events to a stream in Kinesis Data Streams. The filter pattern matches any log events with the text `Test` and forwards them to the stream in Kinesis Data Streams. +The following example uses an account-level subscription policy to forward all log events to a stream in Amazon Kinesis Data Streams. The filter pattern matches any log events with the text `Test` and forwards them to the stream in Amazon Kinesis Data Streams. @@ -51 +51 @@ The following example uses an account-level subscription policy to forward all l -###### To create an account-level subscription policy for Kinesis Data Streams +###### To create an account-level subscription policy for Amazon Kinesis Data Streams @@ -158 +158 @@ The `selection-criteria` field is optional, but is important for excluding log g -You can verify that the flow of log events by by using a Kinesis Data Streams shard iterator and using the Kinesis Data Streams `get-records` command to fetch some Kinesis Data Streams records:: +You can verify that the flow of log events by by using a Amazon Kinesis Data Streams shard iterator and using the Amazon Kinesis Data Streams `get-records` command to fetch some Amazon Kinesis Data Streams records:: @@ -169 +169 @@ You can verify that the flow of log events by by using a Kinesis Data Streams sh -You might need to use this command a few times before Kinesis Data Streams starts to return data. +You might need to use this command a few times before Amazon Kinesis Data Streams starts to return data. @@ -171 +171 @@ You might need to use this command a few times before Kinesis Data Streams start -You should expect to see a response with an array of records. The **Data** attribute in a Kinesis Data Streams record is base64 encoded and compressed with the gzip format. You can examine the raw data from the command line using the following Unix commands: +You should expect to see a response with an array of records. The **Data** attribute in a Amazon Kinesis Data Streams record is base64 encoded and compressed with the gzip format. You can examine the raw data from the command line using the following Unix commands: @@ -210 +210 @@ The key elements in the data structure are the following: -Data messages will use the "DATA_MESSAGE" type. Sometimes CloudWatch Logs might emit Kinesis Data Streams records with a "CONTROL_MESSAGE" type, mainly for checking if the destination is reachable. +Data messages will use the "DATA_MESSAGE" type. Sometimes CloudWatch Logs might emit Amazon Kinesis Data Streams records with a "CONTROL_MESSAGE" type, mainly for checking if the destination is reachable. @@ -257 +257 @@ Before you create the Lambda function, calculate the volume of log data that wil -Ensure that you have set up the Lambda execution role. For more information, see [Step 2.2: Create an IAM Role (execution role)](https://docs.aws.amazon.com/lambda/latest/dg/walkthrough-custom-events-create-test-function.html) in the _AWS Lambda Developer Guide_. +Ensure that you have set up the Lambda execution role. For more information, see [Step 2.2: Create an IAM Role (execution role)](https://docs.aws.amazon.com/lambda/latest/dg/lambda-intro-execution-role.html) in the _AWS Lambda Developer Guide_. @@ -358 +358 @@ The key elements in the data structure are the following: -Data messages will use the "DATA_MESSAGE" type. Sometimes CloudWatch Logs might emit Kinesis Data Streams records with a "CONTROL_MESSAGE" type, mainly for checking if the destination is reachable. +Data messages will use the "DATA_MESSAGE" type. Sometimes CloudWatch Logs might emit Amazon Kinesis Data Streams records with a "CONTROL_MESSAGE" type, mainly for checking if the destination is reachable.