Amazon WorkSpaces Personal introduces unique DNS names for PrivateLink endpoints

Amazon WorkSpaces Personal has introduced unique DNS names for each AWS PrivateLink VPC endpoint, enabling deployment across multiple VPCs and accounts without DNS conflicts.

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 development allows enterprise users to deploy WorkSpaces across multiple AWS VPCs and accounts without encountering DNS resolution conflicts.

Previously, interface VPC endpoints shared a generic DNS name across all endpoints, which could lead to conflicts in multi-account environments. Now, each endpoint receives a globally unique AWS-managed DNS name. This improvement facilitates proper traffic routing in environments with centralized DNS infrastructures, enabling customers to deploy WorkSpaces Personal directories across different VPCs and AWS accounts while preserving security isolation.

The newly assigned DNS names are publicly resolvable but translate to private IP addresses, ensuring they are accessible only from within their respective VPCs. AWS manages these unique DNS names automatically throughout their lifecycle, removing the need for additional Route 53 configurations or custom DNS management.

This feature is available in all AWS regions where PrivateLink is offered for Amazon WorkSpaces Personal. Customers can find more information in the Amazon WorkSpaces PrivateLink documentation and the WorkSpaces Administration Guide for configuration specifics. Existing users will benefit from this enhancement as it maintains compatibility with previous DNS settings.