-
Notifications
You must be signed in to change notification settings - Fork 204
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
-profile options missing #1
Comments
Hi, Thanks for mentioning this. I'm working on an update to have this included. |
The documentation is mentioning that roles are support, but there is no input switch for this? Would be great if this could be integrated though? |
aws-es-proxy supports the |
Hey keot, thank you very much. But are you sure that also roles are supported? Pointing to es-test via AWS_PROFILE does give me an error: {"Message":"User: anonymous is not authorized to perform: es:ESHttpGet on resource: xxx-elk"} [xxx-logon] [es-test] |
Ok, doing the assume role by myself and storing the credentials in $env does work though: $env:AWS_ACCESS_KEY_ID=$tempcred.Credentials.AccessKeyId |
It seems no further actions are needed here. |
…gion (abutaha#1) hard-coded proxy.service value to "es" added insecure flag and logic to avoid SSL verification
I would like to be able to select the AWS profile to use when starting the proxy.
Currently the profile used is 'default'.
Currently if one uses several profile for same account, the proxy may fails to start with the right credentials.
Like with the awscli, it would be nice to be able to select the profile at the command line.
The text was updated successfully, but these errors were encountered: