Skip to main content

AWS IAM Identity Center

Connection

Setup

1

Create an IAM user

Create an IAM user in the account your Identity Center instance runs in, and give it an access key.
2

Allow the actions

Attach a policy allowing the actions under Permissions.

Permissions

Allow these actions for the IAM user, or for the role Klef assumes when the connection names one.
  • sso:ListInstances, sso:ListPermissionSets, sso:DescribePermissionSet and sso:ListAccountsForProvisionedPermissionSet, to read the instance and its permission sets.
  • sso:ListAccountAssignments and sso:ListAccountAssignmentsForPrincipal, to read account assignments.
  • sso:CreateAccountAssignment, sso:DeleteAccountAssignment, sso:DescribeAccountAssignmentCreationStatus and sso:DescribeAccountAssignmentDeletionStatus, to assign and remove permission sets.
  • identitystore:ListUsers and identitystore:DescribeUser, to read users.
  • identitystore:GetUserId, identitystore:CreateUser and identitystore:DeleteUser, to create and delete users.
  • iam:SimulatePrincipalPolicy, which the connection test uses to check the others.
organizations:ListAccounts is optional. It lets Klef offer and name every account in the organization. Without it, Klef offers only the accounts that already hold a permission set.

Settings

aws_identity_center.user

Fields

Default Account Matching Rules

When Klef adopts an account that already exists in AWS IAM Identity Center, it works out whose it is by trying these in order. A connection can override them.

Examples

Cloud access for engineers

AWS permission sets and Azure roles for engineers, read-only in production with just-in-time Contributor, removed when they leave.