AWS iot-sitewise documentation change
Summary
Added dual-stack (IPv4/IPv6) support information for AWS IoT SiteWise VPC interface endpoints
Security assessment
The addition of IPv6 support for VPC endpoints enhances network security capabilities by enabling modern IP stack configurations. While not fixing a specific vulnerability, it documents expanded security-related infrastructure options using AWS PrivateLink. VPC endpoints are a security best practice for private network access.
Diff
diff --git a/iot-sitewise/latest/userguide/vpc-interface-endpoints.md b/iot-sitewise/latest/userguide/vpc-interface-endpoints.md index c27fc9fda..377489cc5 100644 --- a//iot-sitewise/latest/userguide/vpc-interface-endpoints.md +++ b//iot-sitewise/latest/userguide/vpc-interface-endpoints.md @@ -7 +7 @@ -An _interface VPC endpoint_ establishes a private connection between your virtual private cloud (VPC) and AWS IoT SiteWise. [AWS PrivateLink](https://aws.amazon.com/privatelink/) powers interface endpoints, enabling private access to AWS IoT SiteWise API operations. You can bypass the need for an internet gateway, NAT device, VPN connection, or AWS Direct Connect. Instances in your VPC don't need public IP addresses to communicate with AWS IoT SiteWise API operations. Traffic between your VPC and AWS IoT SiteWise doesn't leave the AWS network. +An _interface VPC endpoint_ establishes a private connection between your virtual private cloud (VPC) and AWS IoT SiteWise. [AWS PrivateLink](https://aws.amazon.com/privatelink/) powers interface endpoints, enabling private access to AWS IoT SiteWise API operations. AWS IoT SiteWise supports both IPv4 and IPv6 (dual-stack) through its interface endpoints. You can bypass the need for an internet gateway, NAT device, VPN connection, or AWS Direct Connect. Instances in your VPC don't need public IP addresses to communicate with AWS IoT SiteWise API operations. Traffic between your VPC and AWS IoT SiteWise doesn't leave the AWS network.