Skip to main content
EKS managed add-ons are operational software components for the cluster that AWS manages, patches, and updates. The module installs add-ons through the addons variable.

Supported Add-ons

Common add-ons managed through this module:
To list all available add-ons for your cluster version, run:

Basic Add-on Configuration

Add-ons are configured as a map where the key is the add-on name. An empty object {} installs the add-on with defaults (most_recent = true).

before_compute Flag

Some add-ons must be installed before any nodes join the cluster. Set before_compute = true on these add-ons to ensure they are created before node groups or Fargate profiles.
Add-ons with before_compute = true are created using a separate aws_eks_addon.before_compute resource that has an explicit dependency on the cluster being active but before any dataplane_wait_duration delay. Add-ons without this flag wait for the dataplane wait period to complete.

Version Management

Most Recent Version (Default)

By default, most_recent = true installs the latest available version of each add-on at apply time.

Pinned Version

Pin to a specific add-on version by setting addon_version. This prevents unexpected updates:

Conflict Resolution

Control how the EKS service handles conflicts between add-on managed configuration and any custom configuration that exists in the cluster.

Custom Configuration Values

Pass a JSON string to configuration_values to override add-on settings. The available schema is add-on and version specific.

Discover the Configuration Schema

CoreDNS Example

VPC CNI Example


Pod Identity Association

EKS Pod Identity is the recommended way to grant add-ons IAM permissions without IRSA. Use pod_identity_association inside an add-on block to associate an IAM role with the add-on’s service account.

preserve Flag

The preserve flag (default true) controls whether the add-on is preserved on the cluster when Terraform destroys the add-on resource. When true, the add-on is not removed from the cluster on destroy, preventing disruption to running workloads.

Full Example: EKS Managed Node Group with Add-ons


Add-on Variable Reference