aws-ia/eks-blueprints-addons

Terraform module which provisions addons on Amazon EKS clusters.

Terraform module
AWS
available
Placeholder. This template is not in the library yet. Deploy opens the platform so you can start from your own repository; tell us there if you want this one.
Downloads
7.9M
Version
1.24.3
Published
2026-07-07
License
Apache-2.0
Maintainer
aws-ia

About

Terraform module which provisions addons on Amazon EKS clusters.

Maintained by aws-ia on the Terraform Registry. Latest version 1.24.3, 7.9M downloads. Requires providers: aws >= 5.0; helm >= 3.0; kubernetes >= 2.20; random >= 3.6; time >= 0.9.

Deploy creates a StackGuardian workflow from the module's GitHub repository, pinned to this version. You set the inputs, see the plan, then approve the apply.

Use cases

  • A managed cluster per team or environment, created the same way every time.
  • Platform add-ons installed after the cluster, in order, with approval between.
  • Cluster upgrades run as reviewed changes rather than hand-rolled commands.

Inputs

Required inputs:

  • cluster_name — string
  • cluster_endpoint — string
  • cluster_version — string
  • oidc_provider_arn — string

85 inputs, 32 outputs in total. The full list, with defaults and descriptions, is on the registry page.

What it creates

  • helm_release
  • aws_eks_addon
  • kubernetes_config_map_v1
  • kubernetes_config_map_v1_data
  • aws_iam_policy × 2
  • aws_iam_role_policy_attachment × 3
  • aws_cloudwatch_event_rule × 2
  • aws_cloudwatch_event_target × 2
  • aws_cloudwatch_log_group × 2
  • aws_cloudformation_stack

How it runs on StackGuardian

Terraform workflow from the module's GitHub repository: plan, policy check, approval, then apply.

Plan
Policy check
Approval
Apply

Approvals happen in StackGuardian. An agent can never approve its own run. Every run keeps its plan, policy results and approver in the audit log.

Pick a template. Deploy it with guardrails.