---
title: Elastic Maps HTTP configuration
description: 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,...
url: https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/http-configuration
products:
  - Elastic Cloud on Kubernetes
applies_to:
  - Elastic Cloud on Kubernetes: Generally available
---

# Elastic Maps HTTP configuration
## Load balancer settings and TLS SANs

By default a `ClusterIP` [service](https://kubernetes.io/docs/concepts/services-networking/service/) is created and associated with the Elastic Maps Server deployment. If you want to expose maps externally with a [load balancer](https://kubernetes.io/docs/concepts/services-networking/service/#loadbalancer), it is recommended to include a custom DNS name or IP in the self-generated certificate.
Refer to [Reserve static IP and custom domain](/docs/deploy-manage/security/k8s-https-settings#k8s-static-ip-custom-domain) for more details.

## Provide your own certificate

If you want to use your own certificate, the required configuration is identical to Elasticsearch. Check [Custom HTTP certificate](/docs/deploy-manage/security/k8s-https-settings#k8s-setting-up-your-own-certificate).

## Disable TLS

You can disable the generation of the self-signed certificate and hence disable TLS. Check [Disable TLS](/docs/deploy-manage/security/k8s-https-settings#k8s-disable-tls).

### Ingress and Kibana configuration

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`](/docs/explore-analyze/visualize/maps/maps-connect-to-ems#elastic-maps-server-kibana) 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](https://github.com/elastic/cloud-on-k8s/tree/3.4/config/recipes/) for an example on how to set this up using an Ingress resource.
<admonition title="Support scope for Ingress Controllers">
  [Ingress](https://kubernetes.io/docs/concepts/services-networking/ingress/) is a standard Kubernetes concept. While ECK-managed workloads can be publicly exposed using ingress resources, and we provide [example configurations](https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/recipes), setting up an Ingress controller requires in-house Kubernetes expertise.If ingress configuration is challenging or unsupported in your environment, consider using standard `LoadBalancer` services as a simpler alternative.
</admonition>