- Kibana Guide: other versions:
- What is Kibana?
- Get started
- Set Up Kibana
- Discover
- Visualize
- Dashboard
- Canvas
- Graph data connections
- Machine learning
- Elastic Maps
- Metrics
- Logs
- APM
- Uptime
- SIEM
- Dev Tools
- Stack Monitoring
- Management
- Reporting from Kibana
- REST API
- Kibana plugins
- Limitations
- Release Highlights
- Breaking Changes
- Release Notes
- Developer guide
Connecting to Elastic Maps Service
editConnecting to Elastic Maps Service
editElastic Maps Service (EMS) is a service that hosts tile layers and vector shapes of administrative boundaries. If you are using Kibana’s out-of-the-box settings, Elastic Maps is already configured to use EMS.
EMS requests are made to the following domains:
- catalogue.maps.elastic.co
- tiles.maps.elastic.co
- vector.maps.elastic.co
Elastic Maps makes requests directly from the browser to EMS.
Connect to Elastic Maps Service from an internal network
editTo connect to EMS when your Kibana server and browser are in an internal network:
-
Set
map.proxyElasticMapsServiceInMaps
totrue
in your kibana.yml file to proxy EMS requests through the Kibana server. - Update your firewall rules to whitelist connections from your Kibana server to the EMS domains listed above.
Coordinate map and region map visualizations do not support map.proxyElasticMapsServiceInMaps
and will not proxy EMS requests through the Kibana server.
Disable Elastic Maps Service
editYou might experience EMS connection issues if your Kibana server or browser are on a private network or behind a firewall. If this happens, you can disable the EMS connection to avoid unnecessary EMS requests.
To disable EMS, change your kibana.yml file.
-
Set
map.includeElasticMapsService
tofalse
to turn off the EMS connection. -
Set
map.tilemap.url
to the URL of your tile server. This configures the default tile layer of Elastic Maps. -
(Optional) Set
map.regionmap
to the vector shapes of the administrative boundaries that you want to use.