How to Import an AWS EKS Identity Provider Config into Terraform

Import AWS EKS Identity Provider Config with Terraback (recommended)

Terraback reverse-engineers your live infrastructure: it reads the Amazon EKS resource with read-only credentials, generates the HCL, and produces the exact import block. Two commands take you from a live AWS EKS Identity Provider Config to managed Terraform.

terraback scan all aws --region us-east-1

terraback aws import --method bulk

The Terraform import block

Terraback emits a Terraform 1.5+ import block like the one below. Because the block lives in your configuration, the import is reviewable in a pull request and repeatable across environments.

import {
  to = aws_eks_identity_provider_config.example
  id = "example-cluster:example-config"
}

Example aws_eks_identity_provider_config configuration

Here is a realistic AWS EKS Identity Provider Config block. Terraback generates a fuller version from your actual resource attributes; this is a minimal, valid starting point.

resource "aws_eks_identity_provider_config" "example" {
  cluster_name = "example-cluster"

  oidc {
    identity_provider_config_name = "example-config"
    issuer_url                    = "https://example.auth0.com/"
    client_id                     = "abcdef0123456789"
    username_claim                = "email"
    groups_claim                  = "groups"
  }
}

Gotchas when importing a AWS EKS Identity Provider Config

• This associates an OIDC identity provider with an existing aws_eks_cluster; the import ID is cluster_name and identity_provider_config_name separated by a colon, and the cluster must already exist.
• Only the oidc type is supported by this resource; do not confuse it with IAM-based aws-auth mapping, which is configured differently.
• Most fields inside the oidc block (issuer_url, client_id, username_claim, groups_claim) are force-new, so editing them after import destroys and re-associates the provider.
• Associating or disassociating an OIDC provider is a slow control-plane operation; import reflects the current state but apply-time changes can take several minutes.

Doing it manually with terraform import

The native approach is to write the aws_eks_identity_provider_config block by hand, then run terraform import aws_eks_identity_provider_config.example <import-id> for every resource, one at a time. That works for a handful of resources, but it does not scale: you author all the HCL yourself and repeat the command for each item. Terraback generates the HCL and the import blocks for your whole account in one pass.

Import other AWS resources