Move your AWS CLI profiles to your phone
Turn ~/.aws/config into a QR code
Only paste config, never ~/.aws/credentials. The text stays in this tab: there is no upload, and the page makes no requests.
No profiles found. Check you pasted the contents of ~/.aws/config, with its [profile …] lines.
On your phone, open CloudConsole and go to Account → Add account → Scan setup QR, or point the camera app at the code. You then approve the sign-in once for each access portal.
[default] region = eu-west-2 [sso-session acme] sso_start_url = https://acme.awsapps.com/start sso_region = eu-west-2 sso_registration_scopes = sso:account:access [profile prod] sso_session = acme sso_account_id = 111122223333 sso_role_name = ReadOnly region = eu-west-2 [profile staging] sso_session = acme sso_account_id = 444455556666 sso_role_name = AdministratorAccess region = us-east-1 [profile prod-deploy] role_arn = arn:aws:iam::111122223333:role/Deploy source_profile = prod [profile old-laptop-user] aws_access_key_id = AKIAIOSFODNN7EXAMPLE aws_secret_access_key = wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY region = us-east-1
Paste ~/.aws/config above, tick the profiles you want and scan the QR code with CloudConsole. Your SSO and role profiles (start URL, account, role, region, role ARN, source profile and external ID) move to the phone; keys never do, and you sign in on the phone with your own identity.
What moves, and what doesn’t
The AWS CLI keeps two files. ~/.aws/config says where to get credentials: IAM Identity Center sessions, account IDs, roles, regions. ~/.aws/credentials holds the credentials themselves: access keys and session tokens. This tool reads only the first kind of information.
| In your config | Moves to the phone |
|---|---|
[sso-session] with sso_start_url, sso_region | Yes: one sign-in for every profile that uses it |
sso_account_id, sso_role_name, region | Yes: the account is added straight after you sign in |
Legacy SSO profiles (sso_start_url in the profile) | Yes |
role_arn + source_profile (+ external_id) | Yes, including role chains |
aws_access_key_id, aws_secret_access_key, aws_session_token | Never: dropped with a warning |
credential_process, credential_source, web_identity_token_file | No: they depend on the laptop or on AWS compute |
How the QR code works
The selected profiles are written as a short list of templates, compressed, and put after the # of a cloudconsole.dev/connect link. Browsers never send that part of a link to a server, so even when the link is opened in a browser the profiles stay on the device. The QR code is drawn in this page by a small built-in encoder; no QR service is called.
When CloudConsole reads the code it shows every account and role first, so you can untick anything. Profiles on the same access portal share one sign-in, and roles are added after the profile they are assumed from. A role whose source isn’t in the code is flagged, and you can pick an account already in the app instead.
Questions
Is it safe to paste my AWS config here?
The page has no server side: the text is read by JavaScript in this tab and never uploaded, and the page makes no network requests after it loads (you can go offline first to be sure). ~/.aws/config normally holds no secrets, only where to sign in. If the tool finds keys anyway, it leaves them out of the QR code and tells you.
What about ~/.aws/credentials?
Don’t paste it. That file holds access keys, and a QR code is the wrong way to move them: anyone who sees the screen could copy them. This tool never puts keys in a QR code. For an IAM user, type the key into the app’s Access keys screen, or better, use IAM Identity Center (AWS SSO) so there is no long-lived key on the phone at all.
Which profiles can be moved?
IAM Identity Center (SSO) profiles, both the sso-session style that aws configure sso writes now and the older style with sso_start_url in the profile, and role profiles that use role_arn with source_profile, including external_id and chains of roles. Profiles that use access keys, credential_process, credential_source or web identity tokens stay on the laptop.
Do I still have to sign in on the phone?
Yes. The QR code only says where to sign in and which account, role and region to use. CloudConsole then asks you to approve the sign-in in your browser, once for each access portal, exactly like aws sso login. Nothing works that your own AWS identity can’t already do.
Can I share the QR code with my team?
Yes, that is what it is for: it holds no secrets, so a team can put one on a wiki page to give everyone the same accounts, roles and regions. Each person still signs in as themselves.
Why does it say the selection is too big?
One QR code holds about 2,300 characters. Untick some profiles and make two codes, or copy the link instead, which has no such limit in practice. Very dense codes can also be slow to scan from a screen, so fewer profiles per code scans faster.
CloudConsole signs in with IAM Identity Center like the AWS CLI, keeps tokens in the phone’s secure storage and talks to AWS directly. Alarms, logs, costs and resources across every account and region.
About the app →