Hi all! I've been trying to set up a datahub proje...
# all-things-deployment
b
Hi all! I've been trying to set up a datahub project with a manually (terraformed) elastic search. the health checks for the front end come up but the gms service keeps returning a 403 (error in thread). i've tried both resource and identity based policies on the es cluster with no luck. has anyone else had this issue?
Copy code
Received 403 from <http://vpc-datahub-domain-xxxxxxxx.us-east-1.es.amazonaws.com:80>. Sleeping 1s
b
hey Cory, are you sure your pods have access to the ElasticSearch instance? e.g are security rules allow it to be accessed?
you can try
exec
-ing in the pod and try access ES from there to see
b
i can exec into the pods in question
no issue
b
can you access elastic search from the pod
by
curl -i HOST:PORT/_cat/indices
b
i still get a 403
b
how did you set up ES? what's the authentication method? is there any access control on ES?
b
in reading the docs, i have the es cluster inside a vpc, and there are some conflicting information about using a resource vs. ip-based policy. ip-based would let us use unsigned requests, but we want to use signed requests. i think this mean i need to give the pod the the ability to sign requests?
b
or you can use usename/password to authenticate