AWS codepipeline documentation change
Summary
Updated links to reference updated section titles for viewing compute logs in the console.
Security assessment
Link updates to match editorial changes in other files. No security implications as the referenced security content about log viewing permissions remains the same.
Diff
diff --git a/codepipeline/latest/userguide/rule-reference-Commands.md b/codepipeline/latest/userguide/rule-reference-Commands.md index 5ec8ccdd5..851612425 100644 --- a//codepipeline/latest/userguide/rule-reference-Commands.md +++ b//codepipeline/latest/userguide/rule-reference-Commands.md @@ -60 +60 @@ Because the isolated build environment is used at the account level, an instance - * The permission needed to view logs in the console is detailed in [Permissions required to view compute logs in the CodePipeline console](./security-iam-permissions-console-logs.html) . In the following example screens, use the **Logs** link to view logs for a successful Commands rule in CloudWatch logs. + * The permission needed to view logs in the console is detailed in [Permissions required to view compute logs in the console](./security-iam-permissions-console-logs.html) . In the following example screens, use the **Logs** link to view logs for a successful Commands rule in CloudWatch logs. @@ -102 +102 @@ In the service role policy statement, scope down the permissions to the pipeline -To view logs in the console using the action details dialog page, the permission to view logs must be added to the console role. For more information, see the console permissions policy example in [Permissions required to view compute logs in the CodePipeline console](./security-iam-permissions-console-logs.html). +To view logs in the console using the action details dialog page, the permission to view logs must be added to the console role. For more information, see the console permissions policy example in [Permissions required to view compute logs in the console](./security-iam-permissions-console-logs.html).