AWS vpn documentation change
Summary
Removed mention of users being unable to perform tasks via AWS Management Console/CLI/API by default, while retaining core statement about default permissions for Client VPN resources.
Security assessment
The change simplifies the explanation of default permissions but does not introduce new security controls, address vulnerabilities, or modify security recommendations. The removed text was redundant with the broader statement about lacking permissions to create/modify resources.
Diff
diff --git a/vpn/latest/clientvpn-admin/security_iam_id-based-policy-examples.md b/vpn/latest/clientvpn-admin/security_iam_id-based-policy-examples.md index 528f7abb2..394bddbc3 100644 --- a//vpn/latest/clientvpn-admin/security_iam_id-based-policy-examples.md +++ b//vpn/latest/clientvpn-admin/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesAllow users to view their own permissions -By default, users and roles don't have permission to create or modify Client VPN 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 Client VPN resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.