Skip to content
Open
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -108,7 +108,7 @@ echo -n $ECR_PASSWORD | docker login -u AWS --password-stdin https://$ACCOUNT_ID

```
## Using AWS Assumed Role instead of normal IAM credentials
You can use the `aws sts assume-role` to utilize AWS assigned roles. This allows for using centralized AWS account management and doesn't rely on AWS IAM accounts.
You can use the `aws sts assume-role` along with `jq` to utilize AWS assigned roles. This allows for using centralized AWS account management and doesn't rely on AWS IAM accounts.

If your assigned cross account role is `arn:aws:iam::0123456789:role/AdminCrossAccount`, you can run the rollowing commands:
```
Expand All @@ -124,4 +124,6 @@ docker run \
--env AWS_ACCESS_KEY_ID=$AWS_ACCESS_KEY_ID \
--env AWS_SECRET_ACCESS_KEY=$AWS_SECRET_ACCESS_KEY \
--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
Copy Markdown
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.

```