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 ECR without AwsAccessKeyId and AwsSecretAccessKey #98

Closed

Conversation

william-tran
Copy link

This allows ECR to be used if a role is already assumed. Fixes #94

@william-tran william-tran force-pushed the wtran/ecr-assumed-role branch from 926602a to bdd6148 Compare February 10, 2020 16:38
@nealedj
Copy link

nealedj commented Feb 10, 2020

Nice to see somebody else had the same issue as me :)

I also raised a few last week to fix this: #96

I went with using an explicit parameter to get the resource to authenticate to ECR rather than relying on the region being set. Not sure which solution is preferable?

This allows ECR to be used if a role is already assumed. Fixes #94

Signed-off-by: Will Tran <[email protected]>
@william-tran william-tran force-pushed the wtran/ecr-assumed-role branch from bdd6148 to 82c8af0 Compare February 11, 2020 19:39
@william-tran william-tran changed the title Use ECR when only aws_region is set Use ECR without AwsAccessKeyId and AwsSecretAccessKey Feb 11, 2020
@vito
Copy link
Member

vito commented Mar 25, 2020

Sorry, but I can't merge this change - see #96 (comment) for an explanation. Thanks for the PR!

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

Successfully merging this pull request may close these issues.

Allow ECR access without aws_access_key_id and aws_secret_access_key
3 participants