AWS codepipeline documentation change
Summary
Removed redundant 'CodePipeline' references from console descriptions and service mentions, making documentation more generic
Security assessment
Changes are purely editorial/terminology updates removing service name redundancy. No security policies, permissions, or vulnerabilities are modified. The IAM policy examples and security guidance remain unchanged in substance.
Diff
diff --git a/codepipeline/latest/userguide/security-iam-id-policies-examples.md b/codepipeline/latest/userguide/security-iam-id-policies-examples.md index bd286aa7a..6d40db243 100644 --- a//codepipeline/latest/userguide/security-iam-id-policies-examples.md +++ b//codepipeline/latest/userguide/security-iam-id-policies-examples.md @@ -9 +9 @@ You can attach policies to IAM identities. For example, you can do the following - * **Attach a permissions policy to a user or a group in your account** – To grant a user permissions to view pipelines in the CodePipeline console, you can attach a permissions policy to a user or group that the user belongs to. + * **Attach a permissions policy to a user or a group in your account** – To grant a user permissions to view pipelines in the console, you can attach a permissions policy to a user or group that the user belongs to. @@ -50 +50 @@ JSON -The following example shows a policy in the 111222333444 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 111222333444 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`: @@ -174 +174 @@ JSON -You can create IAM policies to restrict the calls and resources that users in your account have access to, and then attach those policies to your administrative user. For more information about how to create IAM roles and to explore example IAM policy statements for CodePipeline, see [Customer managed policy examples](./security_iam_id-based-policy-examples.html#customer-managed-policies). +You can create IAM policies to restrict the calls and resources that users in your account have access to, and then attach those policies to your administrative user. For more information about how to create IAM roles and to explore example IAM policy statements for , see [Customer managed policy examples](./security_iam_id-based-policy-examples.html#customer-managed-policies).