# AWS Version of Elasticsearch, issue with GeoIP with Lambda Function **URL:** \ **Category:** Elasticsearch\ **Created:** [June 13, 2017, 4:38pm UTC](https://discuss.elastic.co/t/aws-version-of-elasticsearch-issue-with-geoip-with-lambda-function/89241 "2017-06-13T16:38:36Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![wali\_raheem](https://avatars.discourse-cdn.com/v4/letter/w/6f9a4e/32.png) [@wali\_raheem](https://discuss.elastic.co/u/wali_raheem)\ **Post date:** [June 14, 2017, 4:03pm UTC](https://discuss.elastic.co/t/aws-version-of-elasticsearch-issue-with-geoip-with-lambda-function/89241/4 "2017-06-14T16:03:42Z")
This is good, thank you!! As a final point to this; anyone using AWS Elasticsearch who are interested in using the tile map functionality please note: **Using Elasticsearch with Kibana from AWS violates a term of service in regards to using the maps; so when you try it map will be blank and in the console the tiles images are pointed to [example.com/path/to/image.png](http://example.com/path/to/image.png). Even though you can change the map service provider in the options in Kibana, as of now it will still show as [example.com](http://example.com) and will result in blank map tiles** > [@Kibana tile map not loading (trying to load from example.com)](https://discuss.elastic.co/t/kibana-tile-map-not-loading-trying-to-load-from-example-com/75242/8): > > They aren't allowed to use our tilemap service, per the [terms of service](https://www.elastic.co/elastic-tile-service). Who May Use Elastic Tile Service? Only users of unmodified Kibana binaries obtained directly by Elastic or an authorized distribution point (e.g., downloads and GitHub) are allowed to use the Elastic Tile Service. The version of Kibana they run on their hosted service is modified. --- _[View the full topic](https://discuss.elastic.co/t/aws-version-of-elasticsearch-issue-with-geoip-with-lambda-function/89241)._