Amazon WorkSpaces Personal introduces unique DNS names for PrivateLink

Amazon WorkSpaces Personal has introduced a new feature that assigns unique, publicly resolvable Domain Name System (DNS) names to each AWS PrivateLink Virtual Private Cloud (VPC) endpoint. This update allows enterprise customers to deploy WorkSpaces across multiple AWS VPCs and accounts without encountering DNS resolution conflicts. Previously, all endpoints shared a generic DNS name, but now each interface VPC endpoint receives a globally unique AWS-managed DNS name.

This advancement facilitates proper traffic routing in multi-account environments with centralized DNS infrastructure. It enables customers to deploy WorkSpaces Personal directories across various VPCs and AWS accounts while ensuring security isolation. The unique DNS names eliminate the DNS name collisions that previously hindered the use of separate interface VPC endpoints across different accounts. Despite being publicly resolvable, these DNS names maintain security by resolving to private IP addresses, which are only accessible from within the respective VPC.

The management of these unique DNS names is handled automatically by AWS throughout their lifecycle, eliminating the need for additional Route 53 configuration or custom DNS management. This feature is now available in all AWS regions where PrivateLink is supported in Amazon WorkSpaces Personal.

For more information, customers can refer to the Amazon WorkSpaces PrivateLink documentation. Detailed configuration instructions are available in the WorkSpaces Administration Guide. Existing customers will automatically benefit from this enhancement, as the system remains compatible with previous DNS configurations.