AWS transform documentation change
Summary
Removed mention of specific interfaces (Management Console, CLI, API) from default permissions explanation while maintaining core IAM policy guidance
Security assessment
The change simplifies the description of default permissions but doesn't address a specific vulnerability or weakness. While IAM policies are security-related, this edit appears to be a documentation refinement rather than a response to a security incident
Diff
diff --git a/transform/latest/userguide/security_iam_id-based-policy-examples.md b/transform/latest/userguide/security_iam_id-based-policy-examples.md index af73cfbd2..2fb993c82 100644 --- a//transform/latest/userguide/security_iam_id-based-policy-examples.md +++ b//transform/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 AWS Transform 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 Transform resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.