IAM Identity Center is now the front door through which most people reach AWS accounts, so an over-broad permission set, an unwatched SCIM token or a loosely delegated administrator becomes a door into every account in the organisation. This guide goes deeper than the general multi-cloud material: it covers organisation and account instances, permission set design, the AWSReservedSSO roles the service creates, SCIM provisioning from an external identity provider, delegated administration, logging and the hardening settings that matter. It is written for cloud platform engineers, IAM teams and security architects who run or audit an AWS Organizations estate.
This is an independent guide from NHI Mgmt Group, based on AWS's public documentation as of November 2026. It is not sponsored or reviewed by AWS. Product features change, so confirm settings against AWS's current documentation.
Key takeaways
- Use one organisation instance in the management account, delegate day-to-day administration to a member account, and block account instances where you do not want them.
- Permission sets are policy templates, not roles: the service creates an AWSReservedSSO role in every assigned account, and that role can be deleted and recreated with a new suffix.
- The identity provider becomes your AWS control plane: with an external IdP, MFA, user lifecycle and group membership are decided there, and the SCIM bearer token is a one-year credential worth protecting.
- Keep sessions short: permission set sessions default to 1 hour and can reach 12 hours, and ending an Identity Center session does not end role sessions already issued.
- Protect the management account separately with dedicated permission sets assigned to named users, not groups, and an emergency access path that has been tested.
How identity and access work in IAM Identity Center
IAM Identity Center connects a workforce identity source to AWS accounts and applications. Users sign in to the AWS access portal, pick an account and a permission set, and receive short-term credentials for the console or the AWS CLI. For the cross-cloud picture and how this compares with Entra ID and Google Cloud, see the Multi-Cloud Identity Guide.
Organisation instances and account instances
An instance is a single deployment of the service. AWS recommends an organisation instance, enabled in the AWS Organizations management account, because only that type supports multi-account access.
| Capability | Organisation instance | Account instance |
|---|---|---|
| Multi-account permissions (permission sets) | Yes | No |
| AWS access portal access to AWS accounts | Yes | No |
| SAML 2.0 customer managed applications | Yes | No |
| Managed by a delegated administrator | Yes | No |
| Encryption at rest with a customer managed KMS key | Yes | No |
| Replication to additional Regions | Yes | No |
| OAuth 2.0 (OIDC) customer managed applications and AWS managed applications | Yes | Yes |
Account instances exist for single-account use cases, but an unmanaged one in a member account is a second identity store nobody reviews. Many organisations deny sso:CreateInstance with a service control policy on member OUs, leaving the management account free to hold the organisation instance. See the AWS Organizations and SCPs Guide.
Identity sources
- Identity Center directory: users and groups created in the service itself. MFA is enforced by Identity Center, which allows up to eight MFA devices per user: two authenticator apps and six FIDO authenticators.
- Active Directory: AWS Managed Microsoft AD or AD Connector. If you move to or from Active Directory with a delegated administrator, the directory must reside in the delegated administrator member account.
- External identity provider: SAML 2.0 for sign-in plus SCIM 2.0 (or manual provisioning) for users and groups. Identity Center MFA is not supported with an external IdP, so authentication strength is entirely the IdP's job. See the Federation and Trust Relationships Guide.
Permission sets and the roles they create
A permission set is a reusable template of IAM policies. It can hold AWS managed policies, AWS managed job function policies, customer managed policies (referenced by name, so the policy must exist in each target account) and an inline policy, plus an optional permissions boundary. When you assign it to an account, the service creates a role with a name of the form AWSReservedSSO_<permission-set-name>_<unique-suffix> under the path /aws-reserved/sso.amazonaws.com/<region>/ (no Region segment when the identity source is in us-east-1). Edits to the permission set are pushed to every account it is provisioned in. The general mechanics of role policies are covered in the AWS IAM Policies and Roles Guide; the short-term credentials themselves are explained in the AWS STS and AssumeRole Guide.
Designing permission sets
| Pattern | When it fits | Trade-off |
|---|---|---|
| Job function sets (ReadOnly, Developer, NetworkAdmin, SecurityAudit) | Most estates; a small catalogue reused across many accounts | Broad policies unless customer managed policies or boundaries narrow them per account |
| Workload or account-specific sets | Regulated or high-value accounts with distinct duties | Catalogue grows fast; needs naming rules and owners |
| ABAC with session tags | Large estates where team, project or cost centre attributes already exist in the IdP | Depends on IdP attribute quality; tag-based policies are harder to review |
| Break-glass or elevated sets | Production changes, incident response | Must be time bound and monitored, ideally through a just-in-time workflow |
For attribute-based access control, Identity Center passes selected attributes as session tags that policies read with aws:PrincipalTag/<key>. An external IdP can send them as SAML attributes named https://aws.amazon.com/SAML/Attributes/AccessControl:<TagKey>. If the same attribute is also mapped on the Attributes for access control page, the Identity Center directory value wins and replaces the SAML value, which is worth knowing when a tag "should" be different.
Admin roles and privileged access
Identity Center administration is privileged access to every account. Whoever can edit a permission set, change an assignment or alter group membership can grant themselves AdministratorAccess anywhere the set is provisioned.
The management account
- Delegate administration: register a member account as delegated administrator so that most tasks happen outside the management account. The delegated administrator cannot modify permission sets provisioned in the management account; those can only be changed from the management account itself.
- Dedicated permission sets: use permission sets that are only ever assigned to the management account, so a change to a shared set cannot silently widen management account access.
- Assign users, not groups: AWS's own guidance is that anyone who can change membership of a group assigned to a management account permission set controls who reaches the management account. Assign named users directly.
- Remember that SCPs do not apply to the management account: guardrails you rely on elsewhere do not protect it, which is why access to it must be minimal.
Separating administrative duties
AWS recommends keeping identity source changes, SCIM token management and session timeout configuration separate from permission set creation and assignment, with distinct administrative permission sets. Tag permission sets and use policy conditions so that, for example, the platform team can manage developer sets but not sets that reach the delegated administrator or security accounts.
| Administrative function | Key actions to scope | Who should hold it |
|---|---|---|
| Identity source and federation | Identity source changes, IdP metadata, sso-directory:CreateBearerToken | Small IAM engineering group, change controlled |
| Permission set catalogue | Create, update and delete permission sets and their policies | Platform or IAM team, through infrastructure as code |
| Account assignments | Create and delete account assignments | Automated request workflow, with approvals for privileged sets |
| Identity Store data | identitystore:Create*, Update*, Delete*, especially CreateGroupMembership | Nobody, when an external IdP is the source of truth |
| Session settings | Access portal session duration, permission set session duration | IAM engineering, reviewed by security |
Temporary elevated access
AWS describes temporary elevated access (just-in-time access) as a supplement to permission sets and MFA for sensitive operations, and lists AWS-validated partner solutions. Before you adopt one, check the resource policies that reference permission set roles (next section), because a JIT tool that removes and re-adds assignments can trigger role recreation. See the JIT Access Guide.
Integrations, API tokens and service accounts
Identity Center is for people. Workloads, pipelines and third parties should use IAM roles with federation, not Identity Center users. But the service itself depends on several machine credentials and references that are easy to overlook.
The SCIM bearer token
The SCIM access token lets the IdP create, update and delete users and groups. It is valid for one year. AWS raises reminders in the console and the AWS Health Dashboard once 90 days or less remain, weekly at first and daily in the last 15 days. When it expires, synchronisation stops and leavers are no longer deprovisioned, which is a security failure rather than an inconvenience. Treat it as a secret: store it only in the IdP, rotate it before the reminders become daily, delete old tokens, and restrict sso-directory:CreateBearerToken with an SCP outside planned rotations. For SCIM mechanics in general, see the SCIM Provisioning Guide.
SCIM attribute rules that cause access problems
- Required attributes: first name, last name, username and display name. Users missing any of them are not provisioned.
- NameID must match Username: the attribute the IdP sends as the SAML Subject NameID must be the one mapped to Username, or sign-in fails.
- Stable externalId: map it to an immutable value such as the directory object ID so entitlements survive a name or email change.
- Single values only: multivalue attributes are not provisioned and cause sync failures.
- Deprovisioning is decided by the IdP: test what your IdP sends when a user is disabled or removed from the AWS application assignment.
Drift through the Identity Store API
Once SCIM is enabled you cannot add or edit users in the console, but the mutating Identity Store APIs remain available to the management account and the delegated administrator. A direct API change is not reliably corrected by SCIM, because SCIM syncs operate on deltas. That is a privilege escalation path: an administrator adds themselves to a privileged group and the IdP never knows. Apply an SCP denying identitystore:Create*, identitystore:Update* and identitystore:Delete* to the delegated administrator account, and alert on those calls in the management account where the SCP cannot reach.
Resource policies that reference permission set roles
If every assignment of a permission set to an account is removed, the service deletes the role. A later assignment creates a new role with a different suffix, and any KMS key policy, bucket policy or Amazon EKS aws-auth ConfigMap that named the old ARN stops matching. AWS recommends EKS access entries instead of the ConfigMap, keeping at least one permanent assignment in accounts whose roles are referenced, and a backup IAM role that the permission set can assume. Where you must reference these roles, match aws:PrincipalArn with an ArnLike wildcard over the suffix rather than the exact ARN.
Logging and detection
Identity Center activity lands in AWS CloudTrail under several event sources. Collect all of them from the management account and the delegated administrator account into the organisation trail. See the AWS CloudTrail Guide.
| Event source | Covers | What to alert on |
|---|---|---|
sso.amazonaws.com | Instance configuration, permission sets, assignments, access portal | Permission set policy changes, new assignments of privileged sets, session duration changes |
identitystore.amazonaws.com, sso-directory.amazonaws.com | Users, groups, memberships, SCIM token management | Any manual membership change when an external IdP is authoritative; bearer token creation outside rotation windows |
identitystore-scim.amazonaws.com | Calls made by the IdP through SCIM | Sync gaps (no events for days), bulk deletions, calls from unexpected source IPs |
sso-oauth.amazonaws.com | OIDC token flows, including CLI sign-in | Unusual volumes of device authorisation or token requests |
signin.amazon.com | Sign-in events: CredentialChallenge, CredentialVerification, UserAuthentication | Repeated failed verifications, new MFA device enrolment (DeviceEnrollmentRequired), sign-in from new locations |
The sign-in events share an AuthWorkflowID that ties one sign-in sequence together, and CredentialType shows which factors were used (values include PASSWORD, TOTP, WEBAUTHN, EXTERNAL_IDP and EMAIL_OTP). A UserAuthentication with only PASSWORD for a directory user means MFA did not happen. In target accounts, actions appear under AWSReservedSSO_* role sessions; correlate the role session name with the Identity Center user to attribute actions to a person. Map detections to ATT&CK T1078.004 Valid Accounts: Cloud Accounts, T1098.003 Additional Cloud Roles and T1484.002 Trust Modification for changes to the identity source or IdP metadata.
Metrics that show it is working
- Standing privileged assignments: count of users with permanent AdministratorAccess or equivalent; the target trends to zero outside break-glass.
- SCIM token age: days until expiry for the active token, alerting well before 30 days.
- Leaver lag: hours between IdP deactivation and removal in Identity Center, measured from SCIM events.
- Manual Identity Store changes: mutating calls not made by SCIM; the target is zero.
- Permission set session length: share of privileged sets above 1 hour.
Hardening baseline
| Setting | Baseline | Why |
|---|---|---|
| Instance type | One organisation instance; SCP deny sso:CreateInstance on member OUs that do not need account instances | No unmanaged identity stores |
| Delegated administrator | Registered member account used for daily administration | Fewer people in the management account |
| Permission set session duration | 1 hour for privileged sets; longer only with a written reason, never above the 12 hour maximum | Limits the value of a stolen session |
| Access portal session duration | Shorter than the 8 hour default for administrators where workable; the maximum is 90 days | Portal sessions mint new role sessions |
| MFA | Directory users: phishing-resistant FIDO authenticators. External IdP: enforce phishing-resistant MFA and device conditions in the IdP | Identity Center MFA does not apply to federated users |
| Management account sets | Dedicated sets, assigned to named users | Group membership changes cannot widen access |
| Identity Store guardrails | SCP deny mutating Identity Store calls and CreateBearerToken in the delegated administrator account | Stops drift and unplanned SCIM tokens |
| Permissions boundaries | Boundary on sets that allow IAM changes | Prevents users creating roles more powerful than their own |
| Emergency access | Direct SAML federation from the IdP to critical accounts, or break-glass IAM principals, tested on a schedule | Access survives an Identity Center disruption |
Rolling out or tightening Identity Center
- Inventory: list every IAM user, SAML provider and role trust policy in every account, and every existing permission set and assignment. Identify account instances.
- Decide the identity source: external IdP for most organisations with an existing workforce directory; Identity Center directory only for small estates without one.
- Build the permission set catalogue as code: start with read-only and developer sets, add privileged sets with boundaries and 1 hour sessions.
- Pilot: enable SCIM for one IdP group and a sandbox OU; verify provisioning, attribute mapping, NameID matching and deprovisioning of a test leaver.
- Deploy guardrails: delegated administrator, Identity Store and bearer token SCPs, and alerting, before broad assignment.
- Migrate in rings: non-production OUs, then production, removing IAM users and old SAML providers as each account moves.
- Roll back safely: keep the emergency access path live during migration; if a permission set change breaks access, revert the code and let reprovisioning restore the previous policies. Never delete the last assignment in an account whose role ARN is referenced elsewhere.
Small versus large organisations: a handful of accounts can run with a few job function sets and the default directory with FIDO keys. Large estates should treat the catalogue as a product with owners, use ABAC from IdP attributes to avoid set explosion, and put privileged assignments behind a just-in-time workflow.
Common misconfigurations
- Groups assigned to management account sets: anyone who can edit that group in the IdP or the Identity Store controls the management account.
- 12 hour administrator sessions: convenient, and exactly what makes a stolen session valuable. Short privileged sessions limit what a stolen session token is worth.
- Assuming that "End sessions" revokes access: ending a user's Identity Center sessions does not end role sessions already issued in the console or CLI. Disabling the user prevents new sessions; existing credentials last until they expire, so incident runbooks also need a role-level revocation step.
- An expired SCIM token: sync silently stops and leavers keep access. Monitor token age rather than relying on reminder emails.
- Exact AWSReservedSSO ARNs in KMS key policies or aws-auth: a reassignment changes the suffix and locks people out of keys or clusters.
Framework mapping
| Framework | Reference | Identity Center control |
|---|---|---|
| NIST CSF 2.0 | PR.AA-01, PR.AA-03, PR.AA-05 | Central identity source, MFA at the IdP, permission set least privilege and review |
| NIST SP 800-53 Rev. 5 | AC-2, AC-6, IA-2, AU-2, AU-6 | SCIM lifecycle, permission sets and boundaries, MFA, CloudTrail event sources and review |
| CIS Controls v8.1 | 5 Account Management, 6 Access Control Management (6.5 MFA for administrative access, 6.7 centralise access control) | Single organisation instance with federated sign-in and enforced MFA |
| ISO/IEC 27001:2022 Annex A | 5.15, 5.16, 5.18, 8.2, 8.5 | Access control policy, identity lifecycle, access rights review, privileged access, secure authentication |
| MITRE ATT&CK v20 | T1078.004, T1098.003, T1484.002 | Detection of cloud account misuse, role grants and identity source changes |
Practitioner checklist
- Confirm a single organisation instance and deny account instance creation where it is not needed.
- Register a delegated administrator and move daily administration out of the management account.
- Give the management account dedicated permission sets assigned to named users only.
- Set privileged permission set sessions to 1 hour and review every set above that.
- Enforce phishing-resistant MFA at the external IdP, or FIDO authenticators in the Identity Center directory.
- Track the SCIM token's expiry, rotate it early, and restrict
CreateBearerTokenwith an SCP. - Deny mutating Identity Store APIs in the delegated administrator account and alert on them in the management account.
- Replace exact AWSReservedSSO ARNs in resource policies with
ArnLikewildcards, and move EKS to access entries. - Build and test an emergency access path that does not depend on Identity Center.
- Add a role session revocation step to incident runbooks, since ending portal sessions does not revoke role credentials.
Standards and references
- AWS: IAM Identity Center permission sets
- AWS: Delegated administration for IAM Identity Center
- AWS: Provision users and groups from an external identity provider using SCIM
- AWS: Referencing permission sets in resource policies, Amazon EKS cluster config maps and AWS KMS key policies
- AWS: Understanding IAM Identity Center sign-in events
- AWS: Set up emergency access to the AWS Management Console
- NIST: SP 800-53 Rev. 5
- MITRE ATT&CK: Valid Accounts: Cloud Accounts
Related NHI Mgmt Group resources: Multi-Cloud Identity Guide · AWS STS and AssumeRole Guide · AWS Organizations and SCPs Guide · SCIM Provisioning Guide · AWS Security Guide