AWS opensearch-service documentation change
Summary
Updated navigation steps in AWS console and corrected CloudWatch log path example
Security assessment
Changes involve UI navigation instructions and example path formatting without addressing security vulnerabilities or introducing security features.
Diff
diff --git a/opensearch-service/latest/developerguide/monitoring-pipeline-logs.md b/opensearch-service/latest/developerguide/monitoring-pipeline-logs.md index 9e76295ab..351c6184c 100644 --- a/opensearch-service/latest/developerguide/monitoring-pipeline-logs.md +++ b/opensearch-service/latest/developerguide/monitoring-pipeline-logs.md @@ -47 +47 @@ You can enable log publishing on existing pipelines, or while creating a pipelin - 2. Choose **Ingestion** in the left navigation pane and select the pipeline that you want to enable logs for. + 2. Choose **Pipelines** in the left navigation pane. @@ -49 +49 @@ You can enable log publishing on existing pipelines, or while creating a pipelin - 3. Choose **Edit log publishing options**. + 3. Choose the pipeline that you want to enable logs, then choose **Actions** , **Edit log publishing options**. @@ -53 +53 @@ You can enable log publishing on existing pipelines, or while creating a pipelin - 5. Either create a new log group or select an existing one. We recommend that you format the name as a path, such as `/aws/**vendedlogs** /OpenSearchIngestion/`pipeline-name`/audit-logs`. This format makes it easier to apply a CloudWatch access policy that grants permissions to all log groups under a specific path such as `/aws/vendedlogs/OpenSearchService/OpenSearchIngestion`. + 5. Either create a new log group or select an existing one. We recommend that you format the name as a path, such as `/aws/**vendedlogs** /OpenSearchIngestion/`pipeline-name`/audit-logs`. This format makes it easier to apply a CloudWatch access policy that grants permissions to all log groups under a specific path such as `/aws/vendedlogs/OpenSearchIngestion`.