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

Use ~/.aws/credentials #372

Closed
kaihendry opened this issue Nov 10, 2017 · 4 comments
Closed

Use ~/.aws/credentials #372

kaihendry opened this issue Nov 10, 2017 · 4 comments
Assignees
Labels

Comments

@kaihendry
Copy link

Been staring at the aws-cli configure breakage and http://docs.aws.amazon.com/AmazonECS/latest/developerguide/ECS_CLI_Configuration.html and I still can't quite figure out how to use the credentials in ~/.aws/credentials.

What am I missing?

@mattmccarty
Copy link

@kaihendry I opened a similar ticket yesterday. It has more to do with using assumed roles, but should still apply to your case. See my examples in the ticket. The issue was opened for v1.0.0 btw.

@PettitWesley
Copy link
Contributor

PettitWesley commented Nov 13, 2017

@kaihendry Apologies lack of clarity on this in our public AWS documentation. We have added a new flag --aws-profile (Env Var: $AWS_PROFILE) that allows you to reference any profile in ~/.aws/credentials.

Let me know if you have any more questions about the configuration/credential related changes in v1.0!

@dbahlbeck
Copy link

I have some trouble using --aws-profile. The AWS profile I'm trying to use does not seem to work if it refers to credentials in a source profile:

[myprofile]
# this profile has an access key

[sandbox]
output = json
region = eu-west-1
role_arn = arn:aws:iam::123456789012:role/ROLE
source_profile = myprofile

It fails with the error: credentials did not contain aws_access_key_id caused by: error when getting key of section 'sandbox': key 'aws_access_key_id' not exists"

@PettitWesley
Copy link
Contributor

PettitWesley commented Dec 5, 2017

@dbahlbeck, strong apologies for the delay in response. This is caused by the issue discussed in #369. It's been fixed with ECS CLI v1.1.0 which was released last week :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants