Received 403 from AWSAuth, invalidating credentials for retrial. ES inside VPC with open access about aws-es-proxy HOT 9 OPEN

Try passing '-no-sign-reqs' and see if that works.

from aws-es-proxy.

Nope, that's a quick 401. Equivalent to me doing,
curl https://vpc-mydomain-randomcharacters.us-east-1.es.amazonaws.com/_cat/indices from the ec2 instance.

from aws-es-proxy.

ok, is the policy open to public or it is open to specific IP?

from aws-es-proxy.

The policy is allowing "*" to the IAM role of the instance, on which I'm running the proxy from

from aws-es-proxy.

I'm getting the same issue
did you ever find a workaround @nikhilo ? thanks 👍

from aws-es-proxy.

i made a fix for in my org's fork of this repo: hysds@c656b87

looks like the proxy parses the endpoint variable to get the values of region and service and region was being set to an empty string

the AWS Elasticsearch endpoint that we're using isn't what the code is expecting:
https://vpce-########-######vpce-#####-######.us-west-#.vpce.amazonaws.com

so i removed that logic and added an additional flag region to set it explicitly

from aws-es-proxy.

@DustinKLo Thank you very much for the fix! Can you please merge your changes in this repository?
@abutaha it will be very helpful for the community to include this fix into the releases.
Thanks

from aws-es-proxy.

i made a fix for in my org's fork of this repo: hysds@c656b87

looks like the proxy parses the endpoint variable to get the values of region and service and region was being set to an empty string

the AWS Elasticsearch endpoint that we're using isn't what the code is expecting:
https://vpce-########-######vpce-#####-######.us-west-#.vpce.amazonaws.com

so i removed that logic and added an additional flag region to set it explicitly

Thanks for pointing it out. Can you please submit a merge request?

from aws-es-proxy.

sure thing @abutaha
#84

from aws-es-proxy.