5

I'm using Elasticsearch service on AWS

Creating an Elasticsearch instance makes endpoint name like https://search-class101-elasticsearch-XXXX.ap-region.es.amazonaws.com,

but i want Elasticsearch domain like https://elasticsearch.mydomain.com/ I'm trying to.

i'm already tried register as a CNAME on route 53

it returns error "invalid certificate" because different domain name

then, can i rename(alias) doamin with https for aws elasticsearch?

JH. Choi
  • 51
  • 1
  • 4
  • You can't CNAME two https endpoint to one another, CNAME only works for HTTP - Ref https://stackoverflow.com/questions/9294215/why-isn-t-it-possible-to-use-a-cname-redirect-with-https – Rafaf Tahsin Sep 04 '19 at 02:38
  • There's an workaround described here - https://aws.amazon.com/blogs/database/set-access-control-for-amazon-elasticsearch-service/ – Rafaf Tahsin Sep 04 '19 at 02:40
  • 1
    I did with route53 plus LB. I add an entry in route53 and then on host-based routing I redirect the request to ELK. – Adiii Sep 04 '19 at 03:58
  • @Adiii So more or less you added a proxy before ES. That seems silly because ES has its own ELB before it. – Daniel Hajduk Jun 26 '20 at 08:53
  • Yes but that was only for kibana endpoints as hard to remember for user but for applications elk own end point should work – Adiii Jun 26 '20 at 09:22

1 Answers1

0

There is a possibility to create a custom endpoint for AWS Elasticsearch: https://docs.aws.amazon.com/elasticsearch-service/latest/developerguide/es-customendpoint.html.

After this has been setup, you can create a Route53 A record for the IP addresses of your custom Elasticsearch endpoint.

enter image description here

To set it up, select your Elasticsearch domain and click "Edit Domain". There you have the possibility to provide the hostname and the certificate for it.

Mika Riekkinen
  • 91
  • 1
  • 5