AWS vpc documentation change
Summary
Removed redundant statement about AWS Management Console/CLI/API access limitations from default permissions explanation
Security assessment
The change simplifies documentation about default IAM permissions without altering security implications. While related to security documentation, there's no evidence this addresses a vulnerability - it merely removes redundant explanations about how permissions relate to different AWS interfaces.
Diff
diff --git a/vpc/latest/privatelink/security_iam_id-based-policy-examples.md b/vpc/latest/privatelink/security_iam_id-based-policy-examples.md index 0cf77a724..40529ca05 100644 --- a//vpc/latest/privatelink/security_iam_id-based-policy-examples.md +++ b//vpc/latest/privatelink/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Control the use of VPC endpointsControl VPC endpoints creation based on the serv -By default, users and roles don't have permission to create or modify AWS PrivateLink 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 PrivateLink resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.