AWS amazonglacier documentation change
Summary
Removed explicit mention of AWS Management Console, AWS CLI, and AWS API as interfaces requiring permissions, simplifying the explanation of default permissions.
Security assessment
The change simplifies existing documentation about default permissions but does not address any specific security vulnerability or introduce new security features. It removes examples of access methods without altering security guidance.
Diff
diff --git a/amazonglacier/latest/dev/security_iam_id-based-policy-examples.md b/amazonglacier/latest/dev/security_iam_id-based-policy-examples.md index eb8a195e7..ce9dc90f4 100644 --- a//amazonglacier/latest/dev/security_iam_id-based-policy-examples.md +++ b//amazonglacier/latest/dev/security_iam_id-based-policy-examples.md @@ -15 +15 @@ Amazon Glacier (original standalone vault-based service) will no longer accept n -By default, users and roles don't have permission to create or modify Amazon Glacier 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 Glacier resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.