Skip to content
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

Closed
emayssat-ms opened this issue Mar 25, 2017 · 7 comments
Closed

-profile options missing #1

emayssat-ms opened this issue Mar 25, 2017 · 7 comments

Comments

@emayssat-ms
Copy link

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.

@abutaha
Copy link
Owner

abutaha commented Apr 18, 2017

Hi,

Thanks for mentioning this. I'm working on an update to have this included.

@markusbecker
Copy link

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?

@keot
Copy link

keot commented Jul 25, 2017

aws-es-proxy supports the AWS_PROFILE environment variable, so just invoke the proxy with AWS_PROFILE=profile_name ./aws-es-proxy-0.4-mac-amd64 …

@markusbecker
Copy link

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]
aws_access_key_id = xxx
aws_secret_access_key = xxx

[es-test]
role_arn = arn:aws:iam::xxxxx:role/es_test
source_profile = xxx-logon

@markusbecker
Copy link

Ok, doing the assume role by myself and storing the credentials in $env does work though:

$env:AWS_ACCESS_KEY_ID=$tempcred.Credentials.AccessKeyId
$env:AWS_SECRET_ACCESS_KEY=$tempcred.Credentials.SecretAccessKey
$env:AWS_SESSION_TOKEN=$tempcred.Credentials.SessionToken

@abutaha
Copy link
Owner

abutaha commented Jan 10, 2018

It seems no further actions are needed here.

@AlJohri
Copy link

AlJohri commented Sep 1, 2018

@abutaha I think this needs to be documented in the README. see #34

phntom pushed a commit to phntom/aws-es-proxy that referenced this issue Feb 16, 2021
…gion (abutaha#1)

hard-coded proxy.service value to "es"
added insecure flag and logic to avoid SSL verification
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants