CloudConsole

Add an IAM user with access keys (and MFA)

Add an IAM user's access key, optionally with an MFA device, when SSO isn't an option.

Use this when your organisation doesn't use IAM Identity Center. Prefer a dedicated IAM user with only the permissions you need on the go.

Access keys screen with Import .csv, name, key ID, secret, region and Use MFA
Access keys

Steps

  1. Tap Use access keys on the welcome screen, or Account → Add account → Access keys.
  2. Optionally give it a Name such as acme-prod. Without one, the account ID is used.
  3. Enter the Access key ID (it starts AKIA) and the Secret access key, or fill them in with Import .csv or Paste from clipboard at the top of the screen (below).
  4. Pick the Region for your resources.
  5. If your policies require MFA, turn on Use MFA and enter the MFA device ARN (for example arn:aws:iam::123456789012:mfa/me) and a 6-digit code.
  6. Tap Check keys. The app asks AWS who the key belongs to (sts:GetCallerIdentity, which needs no permission) and shows Signed in as with the user's ARN. Nothing is saved yet.
  7. Tap Add account to save it. If you change the key or MFA device after the check, the app checks again.

Import the .csv file

When you create an access key in the IAM console, choose Download .csv file and save it to Files (iPhone) or your downloads (Android). In the app, tap Import .csv and pick the file. The app reads the Access key ID and Secret access key columns, including from the older file IAM gave when creating a user, which has more columns.

If that older file includes a console password, the app ignores it and tells you it wasn't used. The file isn't kept: only the key ID and secret go into the form, and the picker's temporary copy is deleted. Delete the downloaded file yourself once the account is added.

Paste from the clipboard

You can copy the key ID on its own, the ID and secret on two lines, a profile from ~/.aws/credentials (aws_access_key_id / aws_secret_access_key, and mfa_serial if present) or a row of the .csv file.

  • Android: when you open the access key screen, or come back to the app while it's open, a banner asks Use the access key from your clipboard?. Tap Use to fill the fields, or Not now.
  • iPhone: iOS asks for permission every time an app reads the clipboard, so the app only reads it when you tap Paste from clipboard. The button appears when the clipboard has text.

If what you pasted included the secret key, the app clears the clipboard afterwards and says so.

An MFA device ARN on the clipboard, or pasted into the key ID or secret field by mistake, goes to the MFA device ARN field and turns on Use MFA.

How MFA works here

With MFA on, the app exchanges your code for a 12-hour session (sts:GetSessionToken) and uses that instead of the key. After 12 hours it asks for a new code. Codes come from an authenticator app or a hardware token; AWS doesn't accept security keys or passkeys for this API.

Where the secret goes

The secret key is stored in the iPhone Keychain or Android Keystore on this phone only, and used only to sign requests to AWS. See Where your credentials are stored.

Errors when adding

  • "That access key ID isn't valid.": the key doesn't exist or was deleted.
  • "The secret access key doesn't match the key ID.": check for a missing or extra character.
  • "Enter the MFA device ARN … and a 6-digit code.": the ARN looks like arn:aws:iam::123456789012:mfa/name, with your 12-digit account ID. It is not the same as the device's display name.
  • "This isn't an IAM access key file.": the .csv you picked doesn't have the Access key ID and Secret access key columns.
  • "No access key or MFA device ARN on the clipboard.": copy the access key ID (and secret) from the IAM console, then tap Paste from clipboard again.

Temporary keys that start ASIA need a session token and expire within hours, so the app doesn't accept them. Use an IAM user's key (AKIA…), SSO or a role instead.

Questions

Can I rotate the key later?

Remove the account in Account → Accounts (the settings icon next to it), then add it again with the new key. Removing an account deletes its key from the phone.

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.