AWS mediatailor documentation change
Summary
Removed redundant statement about default inability to use AWS interfaces without permissions, focusing on core permission requirements
Security assessment
The change removes a redundant explanation about default access restrictions through AWS interfaces. This is a documentation simplification rather than addressing a security vulnerability or weakness. The core security context about IAM policies granting permissions remains intact.
Diff
diff --git a/mediatailor/latest/ug/security_iam_id-based-policy-examples.md b/mediatailor/latest/ug/security_iam_id-based-policy-examples.md index 92f4df23d..f597c9ff2 100644 --- a//mediatailor/latest/ug/security_iam_id-based-policy-examples.md +++ b//mediatailor/latest/ug/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 MediaTailor 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 MediaTailor resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.