AWS batch documentation change
Summary
Removed specific mention of AWS Management Console, CLI, and API from default permissions explanation. Simplified statement about granting permissions via IAM policies.
Security assessment
The change is a documentation clarification that removes redundant details about interfaces (console/CLI/API) but does not address any specific security vulnerability or introduce new security features. It maintains the same security posture by emphasizing IAM policy requirements.
Diff
diff --git a/batch/latest/userguide/security_iam_id-based-policy-examples.md b/batch/latest/userguide/security_iam_id-based-policy-examples.md index 5a4cbaac6..3fa0134f7 100644 --- a//batch/latest/userguide/security_iam_id-based-policy-examples.md +++ b//batch/latest/userguide/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesUsing the consoleAllow users to view their own permissions -By default, users and roles don't have permission to create or modify AWS Batch 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 Batch resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.