AWS AmazonECR documentation change
Summary
Removed references to AWS Management Console, CLI, and API access being restricted by default permissions
Security assessment
Simplifies explanation of default permissions without introducing security fixes or vulnerabilities. Change removes general access method details rather than addressing a specific security issue.
Diff
diff --git a/AmazonECR/latest/userguide/security_iam_id-based-policy-examples.md b/AmazonECR/latest/userguide/security_iam_id-based-policy-examples.md index 8ffda4e46..cc3f083fc 100644 --- a//AmazonECR/latest/userguide/security_iam_id-based-policy-examples.md +++ b//AmazonECR/latest/userguide/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 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 resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.