AWS AmazonCloudWatch documentation change
Summary
Fixed typographical error in punctuation
Security assessment
Change only corrects a quotation mark with no security implications or content modifications.
Diff
diff --git a/AmazonCloudWatch/latest/logs/CloudWatchLogs-Field-Indexing.md b/AmazonCloudWatch/latest/logs/CloudWatchLogs-Field-Indexing.md index fa72bf76d..f8aed6f0c 100644 --- a//AmazonCloudWatch/latest/logs/CloudWatchLogs-Field-Indexing.md +++ b//AmazonCloudWatch/latest/logs/CloudWatchLogs-Field-Indexing.md @@ -13 +13 @@ For example, suppose you have created a field index for `requestId`. Then, any C -You can also leverage your field indexes to create efficient queries of larger numbers of log groups. When you use the `filterIndex` command in your query instead of the `filter` command, the query will run against selected log groups on log events that have field indexes. These queries can scan as many as 10,000 log groups which you choose by specifying as many as five log group name prefixes. If this is a monitoring account in CloudWatch cross-account observability, you can choose all the source accounts or specify individual source accounts to select the log groups”. +You can also leverage your field indexes to create efficient queries of larger numbers of log groups. When you use the `filterIndex` command in your query instead of the `filter` command, the query will run against selected log groups on log events that have field indexes. These queries can scan as many as 10,000 log groups which you choose by specifying as many as five log group name prefixes. If this is a monitoring account in CloudWatch cross-account observability, you can choose all the source accounts or specify individual source accounts to select the log groups".