AWS cost-management documentation change
Summary
Removed explicit mention of console/CLI/API access restrictions from default permissions description
Security assessment
The change simplifies the explanation of default permissions but doesn't address a specific vulnerability or weakness. While related to IAM policies (security documentation), this appears to be a clarification/streamlining of existing content rather than a response to a security incident or addition of security features.
Diff
diff --git a/cost-management/latest/userguide/security_iam_id-based-policy-examples.md b/cost-management/latest/userguide/security_iam_id-based-policy-examples.md index a2dd50c82..f5a51b06d 100644 --- a//cost-management/latest/userguide/security_iam_id-based-policy-examples.md +++ b//cost-management/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 Cost Management 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 Cost Management resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.