Amazon OpenSearch Service now supports Route 53 alias record for custom endpoint

Amazon OpenSearch Service now supports Amazon Route 53 alias records for defining custom domain endpoints. Alias records provide better flexibility when configuring routing to AWS resources. For more information about Route 53 alias records, please see [documentation](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resource-record-sets-choosing-alias-non-alias.html). Previously, customers had to create a CNAME type DNS record to point their custom DNS domain name to the search endpoint exposed by OpenSearch Service. With this launch, along with CNAME support, customers can create a Route 53 alias record of either IPv4 or IPv6 type for their preferred custom endpoint, and point it to their domain’s dual-stack search endpoint. In order to create a Route53 alias record, customers must first configure their Amazon OpenSearch Service domain to use the [dual stack ip address type](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/createupdatedomains.html). Customers can setup Route 53 alias records using the Route 53 APIs. Amazon Route 53 alias support for Amazon OpenSearch Service domains is now available in all AWS regions except AWS GovCloud (US) Regions where Amazon OpenSearch service is available. To learn more about Amazon OpenSearch Service, please visit the [product page](https://aws.amazon.com/opensearch-service/).