AWS mediapackage documentation change
Summary
Removed mention of specific interfaces (AWS Management Console, AWS CLI, AWS API) from default permissions explanation
Security assessment
The change simplifies language about default permissions but doesn't address vulnerabilities or security incidents. The core security concept (default deny principle) remains intact. Removal of interface examples doesn't weaken or strengthen security posture.
Diff
diff --git a/mediapackage/latest/ug/security_iam_id-based-policy-examples.md b/mediapackage/latest/ug/security_iam_id-based-policy-examples.md index 367261db0..8c3930d98 100644 --- a//mediapackage/latest/ug/security_iam_id-based-policy-examples.md +++ b//mediapackage/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 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.