EKS support for authentication using identity providers

[dvulpe]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

EKS now supports OIDC identity providers as a mechanism of Kubernetes API authentication. This is really great news as it makes kubectl access and end user experience similar to the self managed clusters using the identity provider of choice instead of requiring IAM credentials.

The annoucement is here and AWS have introduced three new API calls:

• AssociateIdentityProviderConfig
• DescribeIdentityProviderConfig
• DisassociateIdentityProviderConfig

New or Affected Resource(s)

• aws_eks_identity_provider_config

Potential Terraform Configuration

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key.

resource "aws_eks_identity_provider_config" "config" {
    oidc {
        client_id = ""
        groups_claim = ""
        groups_prefix = ""
        identity_provider_config_name = ""
        issuer_url = ""
        required_claims = {
            "key" = "value"
        }  
       username_claim = ""
       username_prefix = ""
    }
   tags = {
   }
}

References

• Launch blog

[ewbankkit]

Requires AWS SDK v1.37.10:

• Bump github.com/aws/aws-sdk-go from 1.37.4 to 1.37.10 #17616

[willvrny]

I'm happy to attempt adding this as a new resource.

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.