AWS Directory Service now supports AWS PrivateLink for private VPC connectivity

[AWS Directory Service](https://aws.amazon.com/directoryservice/) now supports [AWS PrivateLink](https://aws.amazon.com/privatelink/), enabling you to ensure all API calls to AWS Directory Service are constrained to within the private networks that you specify. This new capability provides private connectivity to both the AWS Directory Service APIs and Directory Service Data APIs, delivering faster network paths, reduced latency, and eliminating public internet-based call patterns. With AWS PrivateLink support, your access to AWS Directory Service APIs can be constrained to the private network connectivity you specify and eliminate any requirements for an internet gateway or NAT device. This encompasses all essential operations such as creating directories, configuring trust relationships, managing user accounts, and adding users to groups. This capability is particularly valuable for organizations that must maintain strict isolation between their workloads and public network connectivity. To establish a private connection, you create an interface Amazon VPC endpoint powered by AWS PrivateLink, which creates requester-managed network interfaces in each enabled subnet to serve as entry points for Directory Service API traffic. This feature is available in all [AWS Regions](https://docs.aws.amazon.com/directoryservice/latest/admin-guide/regions.html) where AWS Directory Service is supported. To learn more, see the AWS [Directory Service documentation](https://docs.aws.amazon.com/directoryservice/latest/admin-guide/vpc-interface-endpoints.html).