Hello Kibana team,
This might be a question right on the boundary of Kibana and AWS but I am not able to find any guidance online. I am hosting Elasticsearch and Kibana 6.2.4 on a 3 node EC2 cluster for the whole purpose of utilizing region maps and forecasting (elastic cloud does not offer neither at the moment ).
I am hosting all my custom region maps as geojson files in a public S3 bucket.
Looking at the network traffic leaving the Kibana - EC2 instance I see requests towards the public bucket.
I enabled access logging in this public S3 bucket and I do not see Kibana's requests reaching it.
As a result I do not see any map output on my region map visualization
Can anyone guide me and help me pinpoint the issue? Could it be S3 policy related?
For this cluster I have very limited
inbound access policies in place (
port 9200 for ES API,
port 9300 for internal ES communication and
port 9047 for Dremio) and
all traffic for outbound (which should be the case for Kibana region map requests accessing the external S3 bucket).
Do I need a specific rule on the inbound as well? What is the most secure way to accomplish this?
Thank you in advance,