AWS snowball documentation change
Summary
Removed mention of users being unable to perform tasks via AWS Management Console, CLI, or API by default. Simplified explanation about IAM policies granting permissions.
Security assessment
The change removes redundant information about default access restrictions but does not address a specific security vulnerability or weakness. The core security documentation about IAM policies remains intact. This appears to be a clarification edit rather than a security-related update.
Diff
diff --git a/snowball/latest/developer-guide/security_iam_id-based-policy-examples.md b/snowball/latest/developer-guide/security_iam_id-based-policy-examples.md index 9d05d34b4..2a7a20f00 100644 --- a//snowball/latest/developer-guide/security_iam_id-based-policy-examples.md +++ b//snowball/latest/developer-guide/security_iam_id-based-policy-examples.md @@ -11 +11 @@ Effective November 7, 2025, AWS Snowball Edge will only be available to existing -By default, users and roles don't have permission to create or modify AWS Snow Family 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 AWS Snow Family resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.