AWS AmazonECR documentation change
Summary
Removed mention of default inability to use AWS Management Console/CLI/API and simplified IAM policy explanation
Security assessment
The change simplifies the default permissions description but does not address a specific security vulnerability or weakness. It removes redundant information about access methods without altering security guidance.
Diff
diff --git a/AmazonECR/latest/public/security_iam_id-based-policy-examples.md b/AmazonECR/latest/public/security_iam_id-based-policy-examples.md index d2feb66c5..4fddac7aa 100644 --- a//AmazonECR/latest/public/security_iam_id-based-policy-examples.md +++ b//AmazonECR/latest/public/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesUsing the consoleAllow users to view their own permissionsA -By default, users and roles don't have permission to create or modify Amazon ECR Public resources. They also can't perform tasks by using the AWS Management Console, AWS Command Line Interface (AWS CLI), or AWS API. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies. The administrator can then add the IAM policies to roles, and users can assume the roles. +By default, users and roles don't have permission to create or modify Amazon ECR Public resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.