AWS prescriptive-guidance documentation change
Summary
Updated author credits and fixed quote formatting in documentation about ECR wildcard permissions
Security assessment
Changes consist of author attribution updates and typo fixes (straight quotes). Maintains existing security guidance about wildcard permissions without adding new security content or addressing vulnerabilities.
Diff
diff --git a/prescriptive-guidance/latest/patterns/monitor-amazon-ecr-repositories-for-wildcard-permissions-using-aws-cloudformation-and-aws-config.md b/prescriptive-guidance/latest/patterns/monitor-amazon-ecr-repositories-for-wildcard-permissions-using-aws-cloudformation-and-aws-config.md index f54d18fdb..bda448273 100644 --- a//prescriptive-guidance/latest/patterns/monitor-amazon-ecr-repositories-for-wildcard-permissions-using-aws-cloudformation-and-aws-config.md +++ b//prescriptive-guidance/latest/patterns/monitor-amazon-ecr-repositories-for-wildcard-permissions-using-aws-cloudformation-and-aws-config.md @@ -9 +9 @@ SummaryPrerequisites and limitationsArchitectureToolsEpicsAttachments - _Created by Vikrant Telkar (AWS), Sajid Momin (AWS), and Wassim Benhallam (AWS)_ + _Vikrant Telkar, Wassim Benhallam, and Sajid Momin, Amazon Web Services_ @@ -15 +15 @@ On the Amazon Web Services (AWS) Cloud, Amazon Elastic Container Registry (Amazo -IAM supports the “`*`” wildcard in both the resource and action attributes, which makes it easier to automatically choose multiple matching items. In your testing environment, you can allow all authenticated AWS users to access an Amazon ECR repository by using the `ecr:*` [wildcard permission](https://docs.aws.amazon.com/lambda/latest/operatorguide/wildcard-permissions-iam.html) in a principal element for your [repository policy statement](https://docs.aws.amazon.com/AmazonECR/latest/userguide/set-repository-policy.html). The `ecr:*` wildcard permission can be useful when developing and testing in development accounts that can't access your production data. +IAM supports the "`*`" wildcard in both the resource and action attributes, which makes it easier to automatically choose multiple matching items. In your testing environment, you can allow all authenticated AWS users to access an Amazon ECR repository by using the `ecr:*` [wildcard permission](https://docs.aws.amazon.com/lambda/latest/operatorguide/wildcard-permissions-iam.html) in a principal element for your [repository policy statement](https://docs.aws.amazon.com/AmazonECR/latest/userguide/set-repository-policy.html). The `ecr:*` wildcard permission can be useful when developing and testing in development accounts that can't access your production data.