AWS AmazonCloudWatch documentation change
Summary
Fixed apostrophe usage in contractions (changed 'don’t' to 'don't', 'doesn’t' to 'doesn't')
Security assessment
Changes are purely grammatical corrections with no impact on security content. The documentation still describes the same log filtering behavior without altering security implications.
Diff
diff --git a/AmazonCloudWatch/latest/monitoring/CloudWatch-Agent-Configuration-File-Details.md b/AmazonCloudWatch/latest/monitoring/CloudWatch-Agent-Configuration-File-Details.md index 9618995e3..cab637d8a 100644 --- a//AmazonCloudWatch/latest/monitoring/CloudWatch-Agent-Configuration-File-Details.md +++ b//AmazonCloudWatch/latest/monitoring/CloudWatch-Agent-Configuration-File-Details.md @@ -723 +723 @@ If you set `retention_in_days` for a log group that already exists, all logs in - * `filters` – Optional. Can contain an array of entries, each of which specifies a regular expression and a filter type to specify whether to publish or drop log entries that match the filter. If you omit this field, all logs in the log file are published to CloudWatch Logs. If you include this field, the agent processes each log message with all of the filters that you specify, and only the log events that pass all of the filters are published to CloudWatch Logs. The log entries that don’t pass all of the filters will still remain in the host's log file, but will not be sent to CloudWatch Logs. + * `filters` – Optional. Can contain an array of entries, each of which specifies a regular expression and a filter type to specify whether to publish or drop log entries that match the filter. If you omit this field, all logs in the log file are published to CloudWatch Logs. If you include this field, the agent processes each log message with all of the filters that you specify, and only the log events that pass all of the filters are published to CloudWatch Logs. The log entries that don't pass all of the filters will still remain in the host's log file, but will not be sent to CloudWatch Logs. @@ -919 +919 @@ Using `event_ids` for filtering is recommended over regex expressions when you n - * `filters` – Optional. Contains an array of entries. Each entry specifies a regular expression and a filter type to specify whether to publish or drop the log entries that match the filter. When the field is included, the agent processes each log message with all of the filters that you specify, and only the log events that pass all filters are published to CloudWatch Logs. The windows event logs that doesn’t pass all of the filters will be dropped and not sent to CloudWatch Logs. The filters section can also be used with other filtering mechanisms like event ids [4624, 4625] and system levels (Information, Error, or Critical) to effectively filter logs and push to CloudWatch. + * `filters` – Optional. Contains an array of entries. Each entry specifies a regular expression and a filter type to specify whether to publish or drop the log entries that match the filter. When the field is included, the agent processes each log message with all of the filters that you specify, and only the log events that pass all filters are published to CloudWatch Logs. The windows event logs that doesn't pass all of the filters will be dropped and not sent to CloudWatch Logs. The filters section can also be used with other filtering mechanisms like event ids [4624, 4625] and system levels (Information, Error, or Critical) to effectively filter logs and push to CloudWatch. @@ -933 +933 @@ In the example agent configuration below: -For the first entry, the agent pushes logs that contain database failure messages, any authentication related activities, and all login events (both successful and failed attempts) to CloudWatch. Any log that doesn’t match this pattern is dropped. +For the first entry, the agent pushes logs that contain database failure messages, any authentication related activities, and all login events (both successful and failed attempts) to CloudWatch. Any log that doesn't match this pattern is dropped.