AWS verified-access documentation change
Summary
Simplified explanation of default permissions for Verified Access resources by removing redundant details about AWS Management Console/CLI/API access
Security assessment
The change removes redundant details about access methods (Console/CLI/API) but doesn't address any specific security vulnerability or weakness. It maintains the same security posture by emphasizing default deny permissions without introducing new security controls or features.
Diff
diff --git a/verified-access/latest/ug/security_iam_id-based-policy-examples.md b/verified-access/latest/ug/security_iam_id-based-policy-examples.md index 5d1ce75bd..01606fb7e 100644 --- a//verified-access/latest/ug/security_iam_id-based-policy-examples.md +++ b//verified-access/latest/ug/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesPolicy for creating Verified Access instancesAllow users to -By default, users and roles don't have permission to create or modify Verified Access 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 Verified Access resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.