AWS vpc documentation change
Summary
Removed JSON policy example using ec2:VpceServiceName condition key
Security assessment
The deletion removes a security policy example but doesn't indicate any vulnerability being addressed. This appears to be content removal rather than security documentation update.
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 9f94e095f..7f3e60596 100644 --- a//vpc/latest/privatelink/security_iam_id-based-policy-examples.md +++ b//vpc/latest/privatelink/security_iam_id-based-policy-examples.md @@ -134,38 +133,0 @@ You can use the `ec2:VpceServiceName` condition key to control what VPC endpoint -JSON - - -**** - - - - { - "Version": "2012-10-17", - "Statement": [ - { - "Effect": "Allow", - "Action": "ec2:CreateVpcEndpoint", - "Resource": [ - "arn:aws:ec2:111111111111:111111111111:vpc/*", - "arn:aws:ec2:111111111111:111111111111:security-group/*", - "arn:aws:ec2:111111111111:111111111111:subnet/*", - "arn:aws:ec2:111111111111:111111111111:route-table/*" - ] - }, - { - "Effect": "Allow", - "Action": "ec2:CreateVpcEndpoint", - "Resource": [ - "arn:aws:ec2:111111111111:111111111111:vpc-endpoint/*" - ], - "Condition": { - "StringEquals": { - "ec2:VpceServiceName": [ - "com.amazonaws.111111111111.s3" - ] - } - } - } - ] - } - -