AWS mediaconvert documentation change
Summary
Removed specific mention of AWS Management Console, AWS CLI, and AWS API from default permission context while maintaining core IAM policy explanation
Security assessment
The change simplifies language about default permissions without altering security meaning. While IAM policies are security-related, this appears to be an editorial clarification rather than addressing a vulnerability or weakness. No evidence of patching a security issue or introducing new security controls.
Diff
diff --git a/mediaconvert/latest/ug/security_iam_id-based-policy-examples.md b/mediaconvert/latest/ug/security_iam_id-based-policy-examples.md index dba205fb1..c96c2be58 100644 --- a//mediaconvert/latest/ug/security_iam_id-based-policy-examples.md +++ b//mediaconvert/latest/ug/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesUsing the consoleAllow users to view their own permissionsE -By default, users and roles don't have permission to create or modify MediaConvert 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 MediaConvert resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.