Is there anyway to create a friendly URL for AWS Elasticsearch domain url?

I tried creating a Route 53 alias record but that didn't work.

You can use route 53 service of AWS, Create record with CNAME and put value as some friendly name like kibana.logs.com or whatever domain you owned.

We don’t support custom SSL certificates, which means that a custom CNAME for an Elasticsearch Service endpoint such as `mycluster.mycompanyname.example` also is not supported.

Ref:

[To see links please register here]

It is still **not** possible on September 2020:

> **Can I use a Custom SSL certificate?**
>
> We don’t support custom SSL certificates, which means that a custom CNAME for an Elasticsearch Service endpoint such as mycluster.mycompanyname.com also is not supported.


[source][1]


[1]:

[To see links please register here]

It is possible as of November 2020:

> 1. Choose **Edit domain**.
> 2. To add a **Custom endpoint**, select the **Enable custom endpoint** check box.
> 3. For **Custom hostname**, enter your preferred custom endpoint hostname. Your custom endpoint hostname should be a fully qualified domain name (FQDN), such as

[To see links please register here]

or example.yourdomain.com.
> 4. For **AWS certificate**, choose the SSL certificate that you want to use for your domain.

[To see links please register here]

Create a wild card certificate like *.youdomain.com (for subdomain setup) or a domain certificate (e.g yourdomain.com) if you have a domain that you want to point to this cluster in ACM.

***Assuming you are going with a subdomain setup. You can follow similar steps for domain setup.***

While creating the ES cluster select the custom domain option and add Custom hostname as your subdomain (e.g: elasticsearch.yourdomain.com) And for certificate chose wildcard certificate from ACM. Or you can edit your cluster and do the same.

If you have cogito auth for kibana You will need also need to follow these steps:

1) Go to Cognito pool
2) Under App integration > App client settings
3) Update Sign-in and sign-out URLs according to your subdomain.

Adding more information to the [answer][2] by [yurez's][1].

**The following step is also important:**

After you enable a custom endpoint for your OpenSearch Service domain, you must create a CNAME mapping in Amazon Route 53 (or your preferred DNS service provider) to route traffic to the custom endpoint and its subdomains. Create the CNAME from the custom endpoint (the name of the record e.g., example.yourdomain.com) to the auto-generated endpoint (the value of the record e.g., vpc-1b1b1b1b1b1b1b1b1b1b1b1b1.us-east-1.es.amazonaws.com). **Without this mapping, your custom endpoint won't work.**

Reference: [Creating a custom endpoint for Amazon OpenSearch Service][3]


[1]:

[To see links please register here]

[2]:

[To see links please register here]

[3]:

[To see links please register here]