AWS cloud-map documentation change
Summary
Removed redundant statement about default lack of permissions through console/CLI/API and simplified default permissions explanation
Security assessment
The change removes a redundant explanation about default access restrictions but does not address any specific security vulnerability or weakness. This is a documentation clarification rather than a security fix. While the topic relates to security policies, the change itself doesn't introduce new security protections or address specific vulnerabilities.
Diff
diff --git a/cloud-map/latest/dg/security_iam_id-based-policy-examples.md b/cloud-map/latest/dg/security_iam_id-based-policy-examples.md index db33086be..3b174a3d2 100644 --- a//cloud-map/latest/dg/security_iam_id-based-policy-examples.md +++ b//cloud-map/latest/dg/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesUsing the consoleAWS Cloud Map console access exampleAllow -By default, users and roles don't have permission to create or modify AWS Cloud Map 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 AWS Cloud Map resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.