AWS workspaces-thin-client documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' in PrivateLink documentation
Security assessment
Branding update for Direct Connect service name. The documentation describes secure VPC access patterns but doesn't introduce new security controls or address vulnerabilities.
Diff
diff --git a/workspaces-thin-client/latest/ag/vpc-interface-endpoints.md b/workspaces-thin-client/latest/ag/vpc-interface-endpoints.md index 696423bfc..d5a74d06f 100644 --- a//workspaces-thin-client/latest/ag/vpc-interface-endpoints.md +++ b//workspaces-thin-client/latest/ag/vpc-interface-endpoints.md @@ -9 +9 @@ ConsiderationsCreate an interface endpointCreate an endpoint policy -You can use AWS PrivateLink to create a private connection between your VPC and Amazon WorkSpaces Thin Client. You can access WorkSpaces Thin Client as a VPC, without the use of an internet gateway, NAT device, VPN connection, or AWS Direct Connect connection. Instances in your VPC don't require public IP addresses to access WorkSpaces Thin Client. +You can use AWS PrivateLink to create a private connection between your VPC and Amazon WorkSpaces Thin Client. You can access WorkSpaces Thin Client as a VPC, without the use of an internet gateway, NAT device, VPN connection, or Direct Connect connection. Instances in your VPC don't require public IP addresses to access WorkSpaces Thin Client.