This functionality is experimental and may be changed or removed completely in a future release. Elastic will take a best effort approach to fix any issues, but experimental features are not subject to the support SLA of official GA features.
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.
If you want to use your own certificate, the required configuration is identical to Elasticsearch. See Custom HTTP certificate.
You can disable the generation of the self-signed certificate and hence disable TLS. See Disable TLS.
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. See the recipe section for an example on how to set this up using an Ingress resource.