AWS vpn documentation change
Summary
Removed mention of specific interfaces (AWS Management Console, AWS CLI, AWS API) where users lack permissions by default, simplifying the explanation of default access restrictions.
Security assessment
The change removes explicit references to interfaces where permissions are denied but does not alter the core security principle of least privilege or address a specific vulnerability. It appears to be a documentation simplification rather than a security-related update.
Diff
diff --git a/vpn/latest/s2svpn/security_iam_id-based-policy-examples.md b/vpn/latest/s2svpn/security_iam_id-based-policy-examples.md index 6d6c8839f..144f44846 100644 --- a//vpn/latest/s2svpn/security_iam_id-based-policy-examples.md +++ b//vpn/latest/s2svpn/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesUsing the console Describe specific Site-to-Site VPN connec -By default, users and roles don't have permission to create or modify Site-to-Site 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 Site-to-Site VPN resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.