AWS AmazonCloudWatch documentation change
Summary
Simplified explanation of IAM policy requirements for Network Synthetic Monitor resource access
Security assessment
The change removes redundant statements about access methods (console/CLI/API) but maintains the core principle of default deny. No security impact or feature addition is evident.
Diff
diff --git a/AmazonCloudWatch/latest/monitoring/security_iam_id-based-policy-examples-nw.md b/AmazonCloudWatch/latest/monitoring/security_iam_id-based-policy-examples-nw.md index 677ce6958..edb06219f 100644 --- a//AmazonCloudWatch/latest/monitoring/security_iam_id-based-policy-examples-nw.md +++ b//AmazonCloudWatch/latest/monitoring/security_iam_id-based-policy-examples-nw.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 Network Synthetic Monitor 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 Network Synthetic Monitor resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.