Repository navigation
Setting up the AWS IAM Identity Center integration via CLI (no wizard) #69943
stevenGravy
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Sharing a CLI walkthrough for setting up the AWS OIDC integration behind
tctl plugins install awsic, for anyone who'd rather script this than use the guided Web UI wizard — useful if you manage AWS resources with your own Infrastructure as Code tooling.Split into what runs in AWS and what runs in Teleport, with each part setting its own values so they can be run independently (e.g. an AWS admin runs Part 1, hands the resulting role ARN to whoever manages the Teleport cluster for Part 2).
Scope
This isn't specific to Okta, Entra ID, or any particular SSO provider — none of the setup below depends on which (if any) external identity provider is handling sign-in.
It does assume the plugin is running in Teleport's hybrid mode for AWS Identity Center: the
aws_oidcintegration here only has the plugin'ssaml_idp_service_provider_namefield unset, which means Teleport manages AWS account assignments and group imports, but does not create or manage users in AWS Identity Center itself — user provisioning is expected to come from elsewhere (an external IdP's own SCIM push, or done manually). Settingsaml_idp_service_provider_nameswitches the plugin to full hand-off mode, where Teleport becomes the SAML identity provider for Identity Center and provisions users directly via SCIM — that's a separate setup from what's covered here.Prerequisites
integrationresources (the preseteditorrole already has this)Part 1 — Run in AWS
Use
discover.teleportas the audience value here and in the trust policy below — this is the value Teleport's AWS OIDC tokens always use.You can confirm this permission list against the current official documentation here: https://goteleport.com/docs/identity-governance/integrations/aws-iam-identity-center/guide/#step-17-configure-aws-integration
Part 2 — Run in Teleport
The SCIM endpoint URL and bearer token come from the AWS IAM Identity Center console under Settings → Identity source → Automatic provisioning — there's no AWS CLI equivalent for that step.
Verify any time with
tctl get plugins/aws-identity-center. To change which OIDC integration a live plugin uses, reinstall rather than edit:tctl plugins delete aws-identity-centerfollowed by the install command above with updated values.All reactions