AWS AmazonCloudWatch documentation change
Summary
Updated VPC endpoint documentation to state IPv6 support is now available in all AWS regions.
Security assessment
Expands documentation for IPv6 VPC endpoints (a security feature enabling private log transfers). No vulnerability is addressed, but security posture improves with broader feature availability.
Diff
diff --git a/AmazonCloudWatch/latest/logs/cloudwatch-logs-and-interface-VPC.md b/AmazonCloudWatch/latest/logs/cloudwatch-logs-and-interface-VPC.md index 233137f44..ad206fd68 100644 --- a//AmazonCloudWatch/latest/logs/cloudwatch-logs-and-interface-VPC.md +++ b//AmazonCloudWatch/latest/logs/cloudwatch-logs-and-interface-VPC.md @@ -9 +9 @@ AvailabilityCreating a VPC endpoint for CloudWatch LogsTesting the connection be -If you use Amazon Virtual Private Cloud (Amazon VPC) to host your AWS resources, you can establish a private connection between your VPC and CloudWatch Logs. You can use this connection to send logs to CloudWatch Logs without sending them through the internet. CloudWatch Logs supports IPv4 VPC endpoints in all Regions, and supports IPv6 endpoints in all Regions except Asia Pacific (Malaysia), Asia Pacific (Thailand), and Mexico (Central). +If you use Amazon Virtual Private Cloud (Amazon VPC) to host your AWS resources, you can establish a private connection between your VPC and CloudWatch Logs. You can use this connection to send logs to CloudWatch Logs without sending them through the internet. CloudWatch Logs supports IPv4 VPC endpoints in all Regions, and supports IPv6 endpoints in all Regions.