An IAM user is a separate username and password in one AWS account, usually with an access key that sits in a developer's home folder for years. Your identity provider knows nothing about it, so your MFA and Conditional Access policies do not apply. When someone leaves, somebody has to remember to delete their IAM user in every account.
Use IAM Identity Center and connect it to the identity provider you already have. People sign in with their work account, pick an AWS account in the access portal and get temporary credentials for it.
Every Northwind developer has an IAM user in each account. The access key in ~/.aws/credentials is 2 years old, and 3 of the users belong to people who have left.
❌ Figure: Bad example - Bad example - Long-lived keys, and nothing removes access when someone leaves
Northwind developers sign in with Entra ID. The AWS-Developers group has the Developer permission set in NonProd and ReadOnly in Prod. Credentials expire after 1 hour.
✅ Figure: Good example - Good example - Access follows group membership in Entra ID and the credentials are short-lived
For Microsoft Entra ID, follow Configure SAML and SCIM with Microsoft Entra ID and IAM Identity Center. You set up 2 connections:
Watch for these:
Give Entra ID groups a permission set in specific accounts. Do not assign individual users.
| Permission set | Entra ID group | Accounts |
|---|---|---|
| Admin | AWS-Admins | Prod, NonProd |
| Developer | AWS-Developers | NonProd |
| ReadOnly | AWS-Developers | Prod |
| SecurityAudit | AWS-Security | Log/Security |
The AWS CLI v2 and the SDKs sign in through the same portal. Run aws configure sso once per profile, then aws sso login whenever the session expires.
aws configure ssoaws sso login --profile prod-readonlyaws s3 ls --profile prod-readonly
See Configuring IAM Identity Center authentication with the AWS CLI.
Identity Center lives in the region where you enable it, and you cannot move it. Switching regions means deleting the instance, recreating permission sets and assignments, and getting a new portal URL.
The instance always lives in the management account. Register the Log/Security account as its delegated administrator, so nobody signs in to the management account to manage users and assignments. A delegated administrator cannot change permission sets provisioned in the management account.
iam:CreateUser and iam:CreateAccessKey. See Do you use service control policies as guardrails in AWS?