Enterprise SSO for AWS Cognito: Beyond Cognito's SAML Limits
Blog post from SSOJet
Amazon Cognito user pools can support B2B SaaS SAML federation by acting as a service provider and issuing JWTs after authentication through customer identity providers such as Okta or Entra, but operational constraints become more significant as tenant counts grow. Key limitations include a maximum of 1,000 identity providers per pool, shared federation request-rate limits, a 100,000-character SAML response cap, case-sensitive and persistent NameID matching that can cause access issues after email changes, and app-client restrictions that require separate clients for IdP-initiated SAML versus local or social logins. Cognito also lacks a SCIM endpoint, meaning customer offboarding does not automatically revoke active refresh tokens unless an external provisioning or revocation workflow is built. Teams using native Cognito federation are advised to automate identity-provider and app-client configuration, preserve full client settings during updates, coordinate certificate rotation through metadata URLs, and use immutable identifiers rather than email addresses for NameID. As enterprise SSO requirements expand, organizations can retain Cognito for user management and token issuance while connecting it to a single upstream OIDC-based SSO service that manages per-customer SAML or OIDC connections, domain routing, SCIM provisioning, and deprovisioning events.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| Platform Engineering | 39 | 2,014 | 399 | 102 | +19% |
| Serverless | 1 | 1,384 | 325 | 108 | +12% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.