You can use a third-party tile hosting service or you can host your own tile service.

But you can change the default in the kibana.yml settings for Kibana. The default basemap in Kibana is hosted by our Elastic Maps Service. You could also directly configure a custom WMS server, right inside your visualization. That custom layer you can then use in your region or coordinate maps visualizations. You can define a single custom tile-server in the kibana.yml. There are two ways to configure Kibana with custom basemaps. If so, you can configure Kibana to use a custom basemap for all your region maps and coordinate maps. Or maybe you just don’t like our basemap style (😢). Or you run Elasticsearch and Kibana in an air-gapped environment. Perhaps Elastic Maps Service is not available in your area. However, that doesn’t mean you are required to use our services. By default, region maps and coordinate maps in Kibana use basemaps from our Elastic Maps Service based on data from Natural Earth and OpenStreetMap. Today let’s talk about using custom basemaps in your coordinate and regions in Kibana.

Previously, we discussed using custom region maps in Kibana. Previous versions of Kibana may use tilemap instead of map.tilemap. Editor's Note (January 16, 2020): This post has been updated to reflect breaking changes to tilemap parameters in version 7 of Kibana.

Garmin custom maps arcgis