Skip to content

Conversation

@scott-hiemstra
Copy link

This pull request is simply a documentation change. It describes how to use a role for authentication instead of requiring an IAM user in the account.

scott-hiemstra and others added 5 commits August 25, 2022 15:40
After working with internal team, found this additional permission was needed to handle KMS key backed secrets.  Allowing this in addition to @scott-hiemstra's 'Assumed' role changes gives us universal coverage.
Update ecs-roles-cf.json
--env AWS_SESSION_TOKEN=$AWS_SESSION_TOKEN \
smithmicro/ecs:latest create-cluster
smithmicro/ecs:latest create-cluster
unset AWS_ACCESS_KEY_ID AWS_SECRET_ACCESS_KEY AWS_SESSION_TOKEN
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would prefer not to show an unset here, even though it is good practice. It clutters the example IMHO.

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.

3 participants