Stitchflow
AWS IAM Identity Center logo

AWS IAM Identity Center SCIM guide

Native SCIM

How to automate AWS IAM Identity Center user provisioning, and what it actually costs

Native SCIM requires Free (included with AWS) plan

Summary and recommendation

AWS IAM Identity Center supports SCIM 2.0 provisioning and is completely free—no additional licensing costs beyond your AWS account. However, the implementation has significant operational limitations that create ongoing management overhead for IT teams.

The core issues: SCIM sync runs every 20-40 minutes (not real-time), multivalue attributes aren't supported, and once SCIM is enabled, you lose the ability to manually manage users through the AWS console. More problematic, Azure AD users face nested group limitations and attribute removal sync issues, while all IdPs must work around the requirement for specific mandatory fields (First name, Last name, Username, Display name). For organizations managing complex AWS multi-account environments with varying permission sets, these constraints force manual workarounds that undermine automation benefits.

While IAM Identity Center's free pricing is attractive, the operational friction from sync delays, attribute limitations, and console lockout creates hidden administrative costs—especially when managing hundreds of users across multiple AWS accounts with different access requirements.

The strategic alternative

Stitchflow provides SCIM-level provisioning through resilient browser automation for AWS IAM Identity Center that addresses these operational challenges with real-time sync, flexible attribute handling, and expert configuration management. Flat pricing under $5K/year, regardless of user count or AWS account complexity.

Quick SCIM facts

SCIM available?Yes
SCIM tier requiredFree
SSO required first?Yes
SSO available?Yes
SSO protocolSAML 2.0
DocumentationOfficial docs

Supported identity providers

IdPSSOSCIMNotes
OktaOIN app with full provisioning
Microsoft Entra IDGallery app with SCIM
Google WorkspaceJIT onlySAML SSO with just-in-time provisioning
OneLoginSupported

The cost of not automating

Without SCIM (or an alternative like Stitchflow), your IT team manages AWS IAM Identity Center accounts manually. Here's what that costs:

Source: Stitchflow customers using AWS IAM Identity Center, normalized to 500 employees:
Orphaned accounts (ex-employees with access)11
Unused licenses11
IT hours spent on manual management/year195 hours
Unused license cost/year$0
IT labor cost/year$11,727
Cost of compliance misses/year$2,680
Total annual financial impact$14,407

The AWS IAM Identity Center pricing problem

AWS IAM Identity Center gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.

Plan Structure

PlanPriceSSOSCIM
AWS IAM Identity CenterFree (included with AWS)

What this means in practice

While the pricing appears attractive, the SCIM implementation's technical constraints create real operational burden:

Attribute limitations: Single-value attributes only - no support for multivalue fields that many organizations use for roles, departments, or project assignments. Custom attributes aren't supported in the SCIM implementation.

Sync frequency: Changes sync every 20-40 minutes, not real-time. For organizations with frequent role changes or emergency access needs, this delay creates security and operational risks.

Management lockout: Once SCIM is enabled, you cannot add or edit users through the IAM Identity Center console. All user management must flow through your IdP, eliminating backup management options.

Additional constraints

Azure AD nested groups
Not supported, forcing flat group structures that don't match organizational hierarchies.
Attribute removal sync
Removed attributes in Azure AD don't sync back to IAM Identity Center, creating attribute drift over time.
Required fields
Users must have First name, Last name, Username, and Display name - no flexibility for service accounts or non-standard user types.
Multi-account complexity
While SCIM handles user provisioning, permission set assignments across multiple AWS accounts still require careful architecture planning.

Summary of challenges

  • AWS IAM Identity Center supports SCIM but only at Free tier ($0)
  • Google Workspace users get JIT provisioning only, not full SCIM
  • Our research shows teams manually provisioning this app spend significant hidden costs annually

What AWS IAM Identity Center actually offers for identity

AWS IAM Identity Center is Amazon's free centralized identity service that comes with every AWS account. The SCIM provisioning is included at no charge, but the real value is in how it integrates with your broader AWS infrastructure:

SCIM 2.0 automated provisioning from any major IdP
SAML single sign-on across all AWS accounts and services
Centralized permission set management across multi-account organizations
Integration with AWS Organizations for account-level access control
Built-in MFA and security policies
Audit logging through AWS CloudTrail
API access for custom integrations and automation

The challenge isn't cost—it's complexity. While SCIM provisioning works reliably for basic user lifecycle management, the real operational burden comes from managing permission sets, account assignments, and the intricate relationships between users, groups, and AWS resources across potentially dozens of accounts.

Many organizations find themselves spending more time configuring and maintaining IAM Identity Center's permission architecture than they save from automated provisioning, especially when users need different access levels across development, staging, and production environments.

What IT admins are saying

Community sentiment on AWS IAM Identity Center's SCIM implementation is mixed, with specific technical frustrations outweighing pricing concerns. Common complaints:

  • Sync delays of 20-40 minutes create security gaps during offboarding
  • Azure AD integration drops nested groups and doesn't sync attribute removals
  • Console lockout after SCIM setup prevents manual user management
  • Complex multi-account permission set mapping across AWS organizations

After enabling SCIM, you lose the ability to add or edit users directly in the IAM Identity Center console. Everything has to flow through your IdP, which can be limiting for one-off situations.

AWS Community Forums

The nested group limitation with Azure AD is a real pain. We had to flatten our entire group structure just to get provisioning working.

Reddit r/aws

The recurring theme

While AWS IAM Identity Center's SCIM is free, the technical limitations and sync delays create operational headaches that force admins to work around the platform rather than with it.

The decision

Your SituationRecommendation
Need SCIM with multivalue attributes or custom fieldsUse Stitchflow: native SCIM doesn't support these features
Using nested groups in Azure ADUse Stitchflow: AWS doesn't sync nested group structures
Need real-time provisioning for securityUse Stitchflow: avoid 20-40 minute sync delays
Happy with basic SCIM, have AWS expertiseUse native SCIM: it's free and covers standard use cases
Small team with minimal AWS complexityManual may work: but monitor for multi-account sprawl

The bottom line

While AWS IAM Identity Center offers free native SCIM, it comes with significant limitations around attribute handling, sync timing, and complex group structures. For organizations that need robust provisioning automation across multiple AWS accounts, Stitchflow delivers full-featured SCIM without the constraints.

Automate AWS IAM Identity Center without the tier upgrade

Stitchflow delivers SCIM-level provisioning through resilient browser automation, backed by 24/7 human in the loop for AWS IAM Identity Center at <$5K/year, flat, regardless of team size.

Works alongside or instead of native SCIM
Syncs with your existing IdP (Okta, Entra ID, Google Workspace)
Automates onboarding and offboarding
SOC 2 Type II certified
24/7 human-in-the-loop monitoring
Book a Demo

Technical specifications

SCIM Version

2.0

Supported Operations

Create, Update, Deactivate, Groups

Supported Attributes

Not specified

Plan requirement

Free

Prerequisites

SSO must be configured first

Key limitations

  • Multivalue attributes not supported (single value per attribute)
  • Users must have First name, Last name, Username, and Display name
  • After SCIM setup, cannot add/edit users in IAM Identity Center console
  • Azure AD: removed attributes not synced back, nested groups not supported
  • Sync every 20-40 minutes (not real-time)
  • Custom attributes not yet supported in SCIM implementation

Configuration for Okta

Integration type

Okta Integration Network (OIN) app with SCIM provisioning

Prerequisite

SSO must be configured before enabling SCIM.

Where to enable

Okta Admin Console → Applications → AWS IAM Identity Center → Provisioning

Required credentials

SCIM endpoint URL and bearer token (generated in app admin console).

Configuration steps

Enable Create Users, Update User Attributes, and Deactivate Users.

Provisioning trigger

Okta provisions based on app assignments (users or groups).

Full SCIM 2.0 support. Create users, update attributes, push groups. Requires paid Okta license with lifecycle management. Rotate token every 90 days recommended.

Native SCIM is available on Free. Use Stitchflow if you need provisioning without the tier upgrade.

Configuration for Entra ID

Integration type

Microsoft Entra Gallery app with SCIM provisioning

Prerequisite

SSO must be configured before enabling SCIM.

Where to enable

Entra admin center → Enterprise applications → AWS IAM Identity Center → Provisioning

Required credentials

Tenant URL (SCIM endpoint) and Secret token (bearer token from app admin console).

Configuration steps

Set Provisioning Mode = Automatic, configure SCIM connection.

Provisioning trigger

Entra provisions based on user/group assignments to the enterprise app.

Sync behavior

Entra provisioning runs on a scheduled cycle (typically every 40 minutes).

Full SCIM 2.0 support. Sync every 40 minutes by default. Nested groups not supported. PowerShell script available for on-demand sync.

Native SCIM is available on Free. Use Stitchflow if you need provisioning without the tier upgrade.

Unlock SCIM for
AWS IAM Identity Center

Stop paying the SCIM Tax for AWS IAM Identity Center. Get enterprise-grade SCIM at a fraction of the enterprise plan cost.

See how it works
Admin Console
Directory
Applications
AWS IAM Identity Center logo
AWS IAM Identity Center
via Stitchflow

Last updated: 2026-01-11

* Pricing and features sourced from public documentation.

Keep exploring

Related apps

Atlassian Jira Service Management logo

Atlassian Jira Service Management

Has SCIM

IT Service Management / ITSM

SCIM StatusIncluded
Manual Cost$11,946/yr

Atlassian Jira Service Management supports SCIM 2.0 for provisioning both support agents and customers, but only with an Atlassian Guard Standard subscription on top of your existing JSM plan. This means paying for two separate subscriptions: JSM ($20-57/agent/month) plus Guard for SCIM functionality. For enterprise teams with 201+ agents, this often results in six-figure annual costs just to enable automated provisioning. The dual subscription model creates significant budget friction for IT teams who need basic user lifecycle management. Without SCIM, you're manually managing agent accounts and customer portal access, creating security gaps when employees change roles or leave. JSM's customer provisioning complexity—requiring specific product access roles and organization mapping—makes manual management even more error-prone for large service desk operations.

View full guide
15Five logo

15Five

Has SCIM

Performance Management / Employee Engagement

SCIM StatusIncluded
Manual Cost$11,754/yr

15Five includes SCIM provisioning on all plans starting at $4/user/month, with full support for creating, updating, and deactivating users across Okta, Entra ID, Google Workspace, and OneLogin. However, 15Five's SCIM implementation has a critical prerequisite: SSO must be configured first, and their documentation explicitly warns against using JIT provisioning alongside SCIM due to duplicate user creation risks. This creates operational friction for IT teams managing performance management rollouts. The SSO-first requirement means you can't test SCIM provisioning in isolation, and the JIT conflict forces you to choose between automated onboarding convenience and reliable user lifecycle management. For HR-driven tools like 15Five that need to maintain accurate manager hierarchies and team structures, these provisioning gaps can disrupt performance review cycles and employee engagement tracking.

View full guide
Dropbox logo

Dropbox

Has SCIM
SCIM StatusIncluded
Manual Cost$11,754/yr

Dropbox Business supports SCIM 2.0 provisioning on Standard plans and above ($15/user/month), with solid integration across major identity providers including Okta, Azure AD, and Google Workspace. However, there's a critical architectural limitation: Dropbox Sign (formerly HelloSign) operates as a separate product that doesn't support SCIM at all, despite being a core part of many organizations' document workflows. This creates a significant provisioning gap for IT teams. While your main Dropbox storage accounts can be automatically managed, any users who need access to Dropbox Sign must be manually provisioned and deprovisioned. For organizations relying on both products, this means maintaining hybrid workflows where some users are automated and others require manual intervention—exactly the kind of inconsistency that leads to compliance issues and security gaps during employee transitions.

View full guide