Amazon Elasticsearch Service now supports defining a custom name for your domain endpoint
Amazon Elasticsearch Service now provides the ability to define a custom endpoint for your domain and associate an SSL certificate from AWS Certificate Manager (ACM). Defining a friendly name makes it easier for your users to access Kibana, and allows you to move to a new domain without updating your clients.
Amazon Elasticsearch Service now provides the ability to define a custom endpoint for your domain and associate an SSL certificate from AWS Certificate Manager (ACM). Defining a friendly name makes it easier for your users to access Kibana, and allows you to move to a new domain without updating your clients.
You can define a custom endpoint when creating a new domain or by editing an existing domain from the Amazon Elasticsearch Service console, or through the Amazon Elasticsearch Service APIs. You can then link the custom endpoint to a certificate in ACM, and create an Alias or CNAME mapping in Route 53, or in your preferred Domain Name System (DNS), to route traffic to the custom endpoint.
The ability to define a custom endpoint is now available in 24 regions globally: US East (N. Virginia, Ohio), US West (Oregon, N. California), AWS GovCloud (US-Gov-East, US-Gov-West), Canada (Central), South America (Sao Paulo), EU (Ireland, London, Frankfurt, Paris, Stockholm, Milan), Asia Pacific (Singapore, Sydney, Tokyo, Seoul, Mumbai, Hong Kong), Middle East (Bahrain), China (Beijing – operated by Sinnet, Ningxia – operated by NWCD), and Africa (Cape Town). Please refer to the AWS Region Table for more information about Amazon Elasticsearch Service availability.
To learn more, please see the documentation.