Assume a role in another account
Reach other accounts and roles from one you've added, like source_profile in ~/.aws/config.
Once you have one account in the app, you can add roles assumed from it. This is how you reach other accounts when you sign in with access keys, or roles outside your SSO permission sets.

Steps
- Go to Account → Add account → Assume a role. (The option appears once you have at least one account.)
- Under From, pick the account whose credentials will assume the role.
- Enter the Role ARN, for example
arn:aws:iam::123456789012:role/ReadOnly. - Optionally give it a Name, pick the region, and tap Check and add.
The app gets 1-hour credentials for the role and renews them as needed. The session name is CloudConsole, which is how it appears in CloudTrail.
What the two sides need
The role's trust policy must trust the account (or user, or role) you assume it from:
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Principal": {
"AWS": "arn:aws:iam::111122223333:root"
},
"Action": "sts:AssumeRole"
}
]
}
And the identity you assume it from needs permission to call sts:AssumeRole on it:
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": "sts:AssumeRole",
"Resource": "arn:aws:iam::123456789012:role/ReadOnly"
}
]
}
Good to know
- Roles can be chained, up to three hops.
- If the trust policy requires MFA, assume the role from an access-key account with MFA turned on.
- If the role's trust policy requires an external ID (
sts:ExternalId), enter it in External ID. - Removing the account a role is assumed from also removes the role.
- A role counts as an account: on the free plan, adding one needs Pro.
Still stuck?
Email [email protected] with what you tried and any message the app showed. Don’t send access keys or secrets. We reply within two working days.