What Identity and Access Management does not support

What Identity and Access Management does not do, one line each.

Last updated 18 November 2026View as Markdown

Policies

  • Condition operators and keys other than those in Policy documents: no …IfExists, no Null, no tag or principal keys. A policy that uses one is refused when you save it.
  • Policies on resources, apart from S3 bucket policies. Permissions are attached to users, groups and roles; a grant made on a resource's Access panel is a policy on the principal.
  • Versions of a policy. Saving a document replaces the old one.
  • Editing a managed policy. Copy its document into a custom policy instead.
  • A grant on a wildcard, such as every zone. Write a policy for that.
  • Access across organizations. A credential belongs to one organization.

Users, groups and roles

  • Changing an IAM user's type, or renaming an IAM user or a role.
  • Groups inside groups.
  • Assigning a preset role after someone has joined. Attach its managed policy instead.

Federation and sign-in

  • Changing an identity provider's accepted audiences in the console; use the CLI, the API or Terraform.
  • Role sessions longer than one hour.
  • Trust policy operators other than StringEquals and StringLike.
  • Single sign-on started at the identity provider (IdP-initiated SAML). Start at the console's sign-in page.
  • Signing in with a passkey alone. The passkey is the second step after the password.
  • Mapping identity provider groups to an organization role. Map them to IAM groups instead.
  • SCIM bulk operations, sorting, ETags and password changes.
  • SCIM deactivation does not deactivate or delete a person's access keys. While the membership is suspended they are refused with 403 Access key principal is not an active member of this organization, and they work again when SCIM reactivates the person. To end them for good, remove the member; see Manage members.
  • Setting Require two-factor sign-in with the CLI. Set it in the console.
  • Signing a member out everywhere from the console. Use dcloud iam members revoke-sessions.
Did this page help you?