AWS mediapackage documentation change
Summary
Removed mention of specific AWS interfaces (Management Console, CLI, API) from default permission explanation while maintaining core IAM policy guidance.
Security assessment
The change simplifies existing security documentation about default permissions but does not address a specific vulnerability or add new security features. The removal of interface examples doesn't weaken security guidance - it retains the core principle of least privilege.
Diff
diff --git a/mediapackage/latest/userguide/security_iam_id-based-policy-examples.md b/mediapackage/latest/userguide/security_iam_id-based-policy-examples.md index 74763446e..a74ae8daa 100644 --- a//mediapackage/latest/userguide/security_iam_id-based-policy-examples.md +++ b//mediapackage/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 MediaPackage 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 MediaPackage resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.