AWS codepipeline documentation change
Summary
Updated documentation to remove 'CodePipeline' from console references and fix a broken sentence about Jenkins integration (missing service name). Changes are primarily editorial/formatting.
Security assessment
The changes are purely editorial, removing redundant service names from console references and fixing a typographical error (missing 'CodePipeline' after 'and'). There is no evidence of addressing a security vulnerability, weakness, or incident. The changes do not introduce new security guidance or alter existing security policies.
Diff
diff --git a/codepipeline/latest/userguide/security_iam_id-based-policy-examples.md b/codepipeline/latest/userguide/security_iam_id-based-policy-examples.md index ff2446e33..a0ee6d037 100644 --- a//codepipeline/latest/userguide/security_iam_id-based-policy-examples.md +++ b//codepipeline/latest/userguide/security_iam_id-based-policy-examples.md @@ -27 +27 @@ To learn how to create a pipeline that uses resources from another account, and - * [Permissions required to use the CodePipeline console](./security-iam-permissions-console.html) + * [Permissions required to use the console](./security-iam-permissions-console.html) @@ -29 +29 @@ To learn how to create a pipeline that uses resources from another account, and - * [Permissions required to view compute logs in the CodePipeline console](./security-iam-permissions-console-logs.html) + * [Permissions required to view compute logs in the console](./security-iam-permissions-console-logs.html) @@ -40 +40 @@ To learn how to create a pipeline that uses resources from another account, and -In this section, you can find example user policies that grant permissions for various CodePipeline actions. These policies work when you are using the CodePipeline API, AWS SDKs, or the AWS CLI. When you are using the console, you must grant additional permissions specific to the console. For more information, see [Permissions required to use the CodePipeline console](./security-iam-permissions-console.html). +In this section, you can find example user policies that grant permissions for various actions. These policies work when you are using the API, AWS SDKs, or the AWS CLI. When you are using the console, you must grant additional permissions specific to the console. For more information, see [Permissions required to use the console](./security-iam-permissions-console.html). @@ -204 +204 @@ JSON -If you configure a pipeline to use Jenkins for build or test, create a separate identity for that integration and attach an IAM policy that has the minimum permissions required for integration between Jenkins and CodePipeline. This policy is the same as the `AWSCodePipelineCustomActionAccess` managed policy. The following example shows a policy for Jenkins integration: +If you configure a pipeline to use Jenkins for build or test, create a separate identity for that integration and attach an IAM policy that has the minimum permissions required for integration between Jenkins and . This policy is the same as the `AWSCodePipelineCustomActionAccess` managed policy. The following example shows a policy for Jenkins integration: @@ -236 +236 @@ You can configure access to pipelines for users and groups in another AWS accoun -The following example shows a policy in the 80398EXAMPLE account that allows users to view, but not change, the pipeline named `MyFirstPipeline` in the CodePipeline console. This policy is based on the `AWSCodePipeline_ReadOnlyAccess` managed policy, but because it is specific to the `MyFirstPipeline` pipeline, it cannot use the managed policy directly. If you do not want to restrict the policy to a specific pipeline, consider using one of the managed policies created and maintained by CodePipeline. For more information, see [Working with Managed Policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_managed-using.html). You must attach this policy to an IAM role you create for access, for example, a role named `CrossAccountPipelineViewers`: +The following example shows a policy in the 80398EXAMPLE account that allows users to view, but not change, the pipeline named `MyFirstPipeline` in the console. This policy is based on the `AWSCodePipeline_ReadOnlyAccess` managed policy, but because it is specific to the `MyFirstPipeline` pipeline, it cannot use the managed policy directly. If you do not want to restrict the policy to a specific pipeline, consider using one of the managed policies created and maintained by . For more information, see [Working with Managed Policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_managed-using.html). You must attach this policy to an IAM role you create for access, for example, a role named `CrossAccountPipelineViewers`: