[Reporting] Tilemap behind firewall

[elasticmachine]

Original comment by @kobelb:

Running Kibana on a server that is blocked from the public internet is causing Reports with Tilemaps to fail.

Witnessed on a customer's server running Kibana 6.1.2

[elasticmachine]

Original comment by @thomasneirynck:

This is because they cannot reach the manifest which contains the metadata for each of the data layer. They can turn this off by setting in the kibana.yml

map.includeElasticMapsService: false

If they need to see a map, they also need to configure an alternative map service with the tilemap.* settings in the kibana.yml, or use as custom WMS-service.

https://www.elastic.co/guide/en/kibana/current/settings.html

[elasticmachine]

Original comment by @kobelb:

@thomasneirynck didn't this used to work by only waiting a certain amount of time before emitting a renderComplete without the map layer actually loaded.

It's becoming a rather common scenario to run reports with tilemaps on them when the server running kibana is firewalled from the internet.

[elasticmachine]

Original comment by @thomasneirynck:

agreed. thats's why we introduced the yml-setting for people to turn off Kibana trying to access EMS

[elasticmachine]

Original comment by @kobelb:

agreed. thats's why we introduced the yml-setting for people to turn off Kibana trying to access EMS

Is this specific requirement to change this setting documented anywhere? The end-user will just end up seeing a Max attempts reached (3) error when attempting to generate the report.

This seems like a really poor user experience that will result in a bunch of discuss topics and support issues.

[elasticmachine]

Original comment by @thomasneirynck:

yeah, you're right, this really needs more documentation. there's a couple of work-arounds now when people deploy on-prem (setting up own tile-server, proxy-ing EMS, setting this flag, ...). Eventually, we want to offer on-prem deployments of EMS too. This would benefit from a blog post for sure too that explains this.

[elasticmachine]

Original comment by @kobelb:

/cc @elastic/kibana-sharing

[elasticmachine]

Pinging @elastic/kibana-gis

[thomasneirynck]

Closing.

It's unlikely we'll make specific updates for tilemap to make this work.

Already, users can configure a custom tilemap for airgapped environments. (and turning of EMS with includeElasticMapsService: false

The maps app to now can be configured to funnel EMS request through the Kibana server and not use CORS.

There's also an outstanding feature request for Maps to support proxying EMS calls.
#29825 t