AWS AmazonCloudWatch documentation change
Summary
Removed standalone 'Concepts' section and replaced with link to dedicated concepts page. Removed detailed explanations of subscription filter components including role ARNs and selection criteria for log loop prevention.
Security assessment
While the removed content included references to security-related configurations (role ARNs, log loop prevention), this appears to be documentation reorganization rather than addressing a specific vulnerability. The infinite loop prevention mention remains in the linked content, indicating no security regression.
Diff
diff --git a/AmazonCloudWatch/latest/logs/Subscriptions.md b/AmazonCloudWatch/latest/logs/Subscriptions.md index 591a80bf1..9846ccbf3 100644 --- a//AmazonCloudWatch/latest/logs/Subscriptions.md +++ b//AmazonCloudWatch/latest/logs/Subscriptions.md @@ -5,2 +4,0 @@ -Concepts - @@ -11 +9 @@ You can use subscriptions to get access to a real-time feed of log events from C -For cross-account and cross-region log consolidation, you can also use CloudWatch Logs Centralization to replicate log data from multiple accounts and regions into a central location. For more information, see [Cross-account cross-Region log centralization](./CloudWatchLogs_Centralization.html). +You can also use CloudWatch Logs centralization to replicate log data from multiple accounts and regions into a central location. For more information, see [Cross-account cross-Region log centralization](./CloudWatchLogs_Centralization.html). @@ -37 +35 @@ Subscription filters might batch log events to optimize transmission and reduce - * Concepts + * [Concepts](./subscription-concepts.html) @@ -52,40 +49,0 @@ Subscription filters might batch log events to optimize transmission and reduce -## Concepts - -Each subscription filter is made up of the following key elements: - -**filter pattern** - - -A symbolic description of how CloudWatch Logs should interpret the data in each log event, along with filtering expressions that restrict what gets delivered to the destination AWS resource. For more information about the filter pattern syntax, see [Filter pattern syntax for metric filters, subscription filters, filter log events, and Live Tail](./FilterAndPatternSyntax.html). - -**destination arn** - - -The Amazon Resource Name (ARN) of the Kinesis Data Streams stream, Firehose stream, or Lambda function you want to use as the destination of the subscription feed. - -**role arn** - - -An IAM role that grants CloudWatch Logs the necessary permissions to put data into the chosen destination. This role is not needed for Lambda destinations because CloudWatch Logs can get the necessary permissions from access control settings on the Lambda function itself. - -**distribution** - - -The method used to distribute log data to the destination, when the destination is a stream in Amazon Kinesis Data Streams. By default, log data is grouped by log stream. For a more even distribution, you can group log data randomly. - -For log group-level subscriptions, the following key element is also included: - -**log group name** - - -The log group to associate the subscription filter with. All log events uploaded to this log group would be subject to the subscription filter, and those that match the filter are delivered to the destination service that is receiving the matching log events. - -For account-level subscriptions, the following key element is also included: - -**selection criteria** - - -The criteria used for selecting which log groups have the account-level subscription filter applied. If you don't specify this, the account-level subscription filter is applied to all log groups in the account. This field is used to prevent infinite log loops.. For more information about the infinite log loop issue, see [Log recursion prevention](./Subscriptions-recursion-prevention.html). - -Selection criteria has a size limit of 25 KB. - @@ -100 +58 @@ Deleting a metric filter -Log group-level subscription filters +Concepts