-
Notifications
You must be signed in to change notification settings - Fork 329
Error running Zipkin with AWS elasticsearch #161
Comments
@devinsba if you have a few mins, can you check this out? otherwise I can
try tomorrow
|
I find a workaround to use |
I don't use the |
Yes I use only domain name but after start he give me 403 Forbidden in UI. Maybe I need some extra permission in my IAM instance profile? |
Ok, your example in the issue does not reflect what you just said. In case we are misunderstanding each other. Instead of:
You use:
It will also need describe permission on the ES domain. I can't give you an exact policy though as I use |
Ok. Sorry for misunderstanding. Basically I start using |
I think we are missing a README here: which should look similar to here (including a link to perms): |
Also in |
I revised the error messages here so that they have more content when something bad happens (Ex at least the response status, which for example 403 could hint at an auth problem) |
Hello guys. I've tried to start zipkin with AWS elasticsearch as a bacend but have such error in UI
ERROR: cannot load service names:
Here is my docker run string
docker run -d --name zipkin -p 9411:9411 -e STORAGE_TYPE=elasticsearch -e ES_AWS_DOMAIN="https://search-elk-test-<SOME-ID>.eu-west-1.es.amazonaws.com" openzipkin/zipkin
I deployed AWS elastic as a public domain so each service has access. Please help.
Thanks
The text was updated successfully, but these errors were encountered: