IntermediateIdentity Provider12 min read

Connect AWS IAM Identity Center to Gateco

Sync AWS IAM Identity Center users and groups with Gateco for policy-aware AI retrieval. Covers IAM policies, Identity Store ID, and credential setup.

Last updated: May 21, 2026

Prerequisites

  • An AWS account with permission to create IAM users and enable IAM Identity Center
  • IAM Identity Center enabled (or permission to enable it) in your AWS Organization
  • Access to the AWS Console

Overview — 6 steps

  1. 1Enable IAM Identity Center
  2. 2Create an IAM user for Gateco
  3. 3Attach the Identity Store read policy
  4. 4Get your Identity Store ID
  5. 5Add credentials to Gateco
  6. 6Trigger initial sync

This guide walks you through connecting AWS IAM Identity Center to Gateco so that your AWS users and groups become available as principals for identity-aware retrieval policies. Once synced, you can write RAG access control rules like "allow members of the engineering group to retrieve documents classified as internal" — enforcing identity-based access at the retrieval layer without any custom logic in your application.

AWS IAM Identity Center integration requires the Growth plan or above. Free and Team plan users can connect a stub IDP for development.

Step 1 — Enable IAM Identity Center

IAM Identity Center must be enabled in your AWS Organization before you can create an Identity Store.

  1. Open the AWS Console and navigate to IAM Identity Center (search "Identity Center" in the top bar).
  2. If prompted, click Enable. This takes about 30 seconds.
  3. Once enabled, go to Settings. Note the Identity Store ID — it looks like d-90660f8614.
  4. Also note the Region where Identity Center is enabled (e.g. us-east-1).

IAM Identity Center must be enabled in the management account of an AWS Organization. If you see a message about creating an organization, follow the prompts to set one up — it is free.

Step 2 — Create an IAM user for Gateco

Create a dedicated IAM user that Gateco will use to read your Identity Store. Keeping this separate from other service accounts makes it easier to audit and rotate credentials.

  1. Navigate to IAM → Users → Create user.
  2. Username: gateco-idp-reader (or any name meaningful to your org).
  3. On the permissions screen, choose "Attach policies directly" — leave all checkboxes empty for now.
  4. Finish creating the user.
  5. Go to the user → Security credentials → Create access key.
  6. Use case: "Application running outside AWS". Click Next.
  7. Copy both the Access Key ID and Secret Access Key immediately — the secret is shown only once.

Step 3 — Attach the Identity Store read policy

Attach an inline policy with the minimum permissions Gateco needs.

  1. Open the IAM user you created → Add permissions → Create inline policy.
  2. Switch to the JSON editor and paste the policy below.
  3. Name the policy gateco-idp-read and save.
json
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "identitystore:ListUsers",
        "identitystore:ListGroups",
        "identitystore:ListGroupMemberships",
        "identitystore:DescribeUser",
        "identitystore:DescribeGroup"
      ],
      "Resource": "*"
    }
  ]
}

All identitystore:* actions require "Resource": "*" — AWS does not support resource-level ARN restrictions for the Identity Store service.

Step 4 — Get your Identity Store ID

You already noted this in Step 1, but here is where to find it if you need it again:

  1. Navigate to IAM Identity Center → Settings.
  2. Under "Identity source", copy the Identity store ID (format d-xxxxxxxxxx).

Step 5 — Add credentials to Gateco

In the Gateco dashboard:

  1. Navigate to Identity Providers → Add provider.
  2. Select AWS IAM Identity Center.
  3. Enter the values from the table below.
  4. Click Test connection. Gateco will display the number of users and groups it can read.
  5. Click Save.
FieldValue
Identity Store IDd-xxxxxxxxxx from IAM Identity Center Settings
AWS RegionThe region where Identity Center is enabled (e.g. us-east-1)
Access Key IDThe access key ID created in Step 2
Secret Access KeyThe secret access key created in Step 2

Step 6 — Trigger initial sync

After saving the provider, click Sync now. Gateco will:

  1. List all users from the Identity Store.
  2. List all groups and their memberships.
  3. Create Principal records for each user.
  4. Populate group assignments and department attributes.

Once synced, principals appear in the Principals list and are available for use in policy conditions (principal.groups, principal.attributes.department, etc.).

AWS IAM Identity Center has no native department field. Gateco reads the UserType attribute and maps it to department. Set UserType on your users to enable department-based policy conditions.

Configuration reference

Config fieldExampleRequired
identity_store_idd-90660f8614Yes
aws_regionus-east-1Yes
aws_access_key_idAKIAIOSFODNN7EXAMPLEYes
aws_secret_access_keywJalrXUtnFEMI/...Yes

Troubleshooting

ErrorCauseFix
AccessDeniedException: identitystore:ListUsersPolicy not attached or not yet propagatedVerify the inline policy exists on the IAM user and wait 10 seconds before retrying
Users sync but department is emptyUserType attribute not set on usersSet UserType on each user in IAM Identity Center (custom attribute under Settings → Attributes for access control)
Connection test fails with "InvalidClientTokenId"Wrong access key or key deletedCreate a new access key and update the credentials in Gateco

Frequently asked questions

What IAM permissions does Gateco need for AWS IAM Identity Center?

Gateco needs five read-only permissions: identitystore:ListUsers, identitystore:ListGroups, identitystore:ListGroupMemberships, identitystore:DescribeUser, and identitystore:DescribeGroup. All require "Resource": "*" because AWS does not support resource-level ARN restrictions for the Identity Store service. These are the only permissions needed to enable identity-aware retrieval — Gateco reads your AWS SSO user and group data once to build principals, then uses them to enforce RAG access control policies locally.

Does the AWS IAM Identity Center integration work on the Gateco Free plan?

No. Connecting a real identity provider (AWS, Azure, GCP, or Okta) requires the Growth plan or above. The Free and Team plans support stub IDP configurations for development and testing only.

How long does the initial sync take for a large organization?

For organizations up to 10,000 users, the initial sync typically completes in under 60 seconds. Subsequent syncs run every 60 minutes by default (configurable in Identity Provider settings). You can also trigger a manual sync at any time.

Ready to add policy-aware retrieval?

Connect your AWS setup to Gateco in under 5 minutes.