This documentation contains work-in-progress information for future Elastic Stack and Cloud releases. Use the version selector to view supported release docs. It also contains some Elastic Cloud serverless information. Check out our serverless docs for more details.

« Advanced configuration Run Enterprise Search on ECK »

› › ›

HTTP configuration

edit

HTTP configuration

edit

This functionality is in technical preview and may be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features.

Load balancer settings and TLS SANs

edit

By default a ClusterIP service is created and associated with the Elastic Maps Server deployment. If you want to expose maps externally with a load balancer, it is recommended to include a custom DNS name or IP in the self-generated certificate.

Refer to Reserve static IP and custom domain for more details.

Provide your own certificate

edit

If you want to use your own certificate, the required configuration is identical to Elasticsearch. Check Custom HTTP certificate.

Disable TLS

edit

You can disable the generation of the self-signed certificate and hence disable TLS. Check Disable TLS.

Ingress and Kibana configuration

edit

To use Elastic Maps Server from your Kibana instances, you need to configure Kibana to fetch maps from your Elastic Maps Server instance by using the map.emsUrl configuration key. The value of this setting needs to be the URL where the Elastic Maps Server instance is reachable from your browser. The certificates presented by Elastic Maps Server need to be trusted by the browser, and the URL must have the same origin as the URL where your Kibana is hosted to avoid cross origin resource issues. Check the recipe section for an example on how to set this up using an Ingress resource.

« Advanced configuration Run Enterprise Search on ECK »