AWS Load Balancer Controller - Amazon EKS
AWS services or capabilities described in AWS documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with AWS services in China.

AWS Load Balancer Controller

The AWS Load Balancer Controller manages AWS Elastic Load Balancers for a Kubernetes cluster. The controller provisions:

  • An AWS Application Load Balancer (ALB) when you create a Kubernetes Ingress.

  • An AWS Network Load Balancer (NLB) when you create a Kubernetes Service of type LoadBalancer using IP targets on 1.18 or later Amazon EKS clusters. If you're load balancing network traffic to instance targets, then you use the in-tree Kubernetes load balancer controller and don't need to install this controller. For more information about NLB target types, see Target type in the User Guide for Network Load Balancers.

The controller was formerly named the AWS ALB Ingress Controller. It is an open source project managed on GitHub. This topic helps you install the controller using default options. You can view the full documentation for the controller on GitHub. Before deploying the controller we recommend that you review the prerequisites and considerations in Application load balancing on Amazon EKS and Network load balancing on Amazon EKS. Those topics also include steps to deploy a sample application that require the controller to provision AWS resources.


An existing cluster. If you don't have an existing cluster, see Getting started with Amazon EKS.

To deploy the AWS Load Balancer Controller to an Amazon EKS cluster

In the following steps, replace the <example values> (including <>) with your own values.

  1. Determine whether you have an existing IAM OIDC provider for your cluster.

    View your cluster's OIDC provider URL.

    aws eks describe-cluster --name <cluster_name> --query "cluster.identity.oidc.issuer" --output text

    Example output:

    List the IAM OIDC providers in your account. Replace <EXAMPLED539D4633E53DE1B716D3041E> (including <>) with the value returned from the previous command.

    aws iam list-open-id-connect-providers | grep <EXAMPLED539D4633E53DE1B716D3041E>

    Example output

    "Arn": "arn:aws:iam::111122223333:oidc-provider/"

    If output is returned from the previous command, then you already have a provider for your cluster. If no output is returned, then you must create an IAM OIDC provider.

    To create an IAM OIDC provider, see Create an IAM OIDC provider for your cluster.

  2. Download an IAM policy for the AWS Load Balancer Controller that allows it to make calls to AWS APIs on your behalf. You can view the policy document on GitHub.

    curl -o iam_policy_cn.json
  3. Create an IAM policy using the policy downloaded in the previous step.

    Take note of the policy ARN that is returned.

  4. Create an IAM role and annotate the Kubernetes service account named aws-load-balancer-controller in the kube-system namespace for the AWS Load Balancer Controller using eksctl or the AWS Management Console and kubectl.


    Use the following command:

    eksctl create iamserviceaccount \ --cluster=my-cluster \ --namespace=kube-system \ --name=aws-load-balancer-controller \ --attach-policy-arn=arn:aws:iam::<AWS_ACCOUNT_ID>:policy/AWSLoadBalancerControllerIAMPolicy \ --override-existing-serviceaccounts \ --approve
    AWS Management Console

    Using the AWS Management Console and kubectl

    1. Open the IAM console at

    2. In the navigation panel, choose Roles, Create Role.

    3. In the Select type of trusted entity section, choose Web identity.

    4. In the Choose a web identity provider section:

      1. For Identity provider, choose the URL for your cluster.

      2. For Audience, choose

    5. Choose Next: Permissions.

    6. In the Attach Policy section, select the AWSLoadBalancerControllerIAMPolicy policy that you created in step 3 to use for your service account.

    7. Choose Next: Tags.

    8. On the Add tags (optional) screen, you can add tags for the account. Choose Next: Review.

    9. For Role Name, enter a name for your role, such as AmazonEKSLoadBalancerControllerRole, and then choose Create Role.

    10. After the role is created, choose the role in the console to open it for editing.

    11. Choose the Trust relationships tab, and then choose Edit trust relationship.

    12. Find the line that looks similar to the following:

      "": ""

      Change the line to look like the following line. Replace <EXAMPLED539D4633E53DE1B716D3041E> (including <>) with your cluster's OIDC provider ID and replace <region-code> with the Region code that your cluster is in.

      "oidc.eks.<region-code><EXAMPLED539D4633E53DE1B716D3041E>:sub": "system:serviceaccount:kube-system:aws-load-balancer-controller"
    13. Choose Update Trust Policy to finish.

    14. Note the ARN of the role for use in a later step.

    15. Save the following contents to a file named aws-load-balancer-controller-service-account.yaml.

      apiVersion: v1 kind: ServiceAccount metadata: labels: controller aws-load-balancer-controller name: aws-load-balancer-controller namespace: kube-system annotations: arn:aws:iam::<AWS_ACCOUNT_ID>:role/AmazonEKSLoadBalancerControllerRole
    16. Create the service account on your cluster.

      kubectl apply -f aws-load-balancer-controller-service-account.yaml
  5. If you currently have the AWS ALB Ingress Controller for Kubernetes installed, uninstall it. The AWS Load Balancer Controller replaces the functionality of the AWS ALB Ingress Controller for Kubernetes.

    1. Check to see if the controller is currently installed.

      kubectl get deployment -n kube-system alb-ingress-controller

      Output (if it is installed). Skip to step 5b.

      NAME READY UP-TO-DATE AVAILABLE AGE alb-ingress-controller 1/1 1 1 122d

      Output (if it isn't installed). If it isn't installed, skip to step 6.

      Error from server (NotFound): deployments.apps "alb-ingress-controller" not found
    2. If the controller is installed, enter the following commands to remove it.

      kubectl delete -f kubectl delete -f
    3. If you removed the AWS ALB Ingress Controller for Kubernetes, add the following IAM policy to the IAM role created in step 4. The policy allows the AWS Load Balancer Controller access to the resources that were created by the ALB Ingress Controller for Kubernetes.

      1. Download the IAM policy. You can also view the policy.

        curl -o iam_policy_v1_to_v2_additional.json
      2. Create the IAM policy and note the ARN returned.

        aws iam create-policy \ --policy-name AWSLoadBalancerControllerAdditionalIAMPolicy \ --policy-document file://iam_policy_v1_to_v2_additional.json
      3. Attach the IAM policy to the IAM role that you created in step 4. Replace <your-role-name> (including <>) with the name of the role. If you created the role using eksctl, then to find the role name that was created, open the AWS CloudFormation console and select the eksctl-<your-cluster-name>-addon-iamserviceaccount-kube-system-aws-load-balancer-controller stack. Select the Resources tab. The role name is in the Physical ID column. If you used the AWS Management Console to create the role, then the role name is whatever you named it, such as AmazonEKSLoadBalancerControllerRole.

        aws iam attach-role-policy \ --role-name eksctl-<your-role name>\ --policy-arn arn:aws:iam::111122223333:policy/AWSLoadBalancerControllerAdditionalIAMPolicy
  6. Install the AWS Load Balancer Controller using Helm V3 or later or by applying a Kubernetes manifest.

    Helm V3 or later
    1. Install the TargetGroupBinding custom resource definitions.

      kubectl apply -k ""
    2. Add the eks-charts repository.

      helm repo add eks
    3. Install the AWS Load Balancer Controller using the command that corresponds to the Region that your cluster is in.


      If you are deploying the controller to Amazon EC2 nodes that you have restricted access to the Amazon EC2 instance metadata service (IMDS) from, or if you are deploying to Fargate, then you need to add the following flags to the command that you run:

      • --set region=<region-code>

      • --set vpcId=<vpc-xxxxxxxx>

      helm upgrade -i aws-load-balancer-controller eks/aws-load-balancer-controller \ --set clusterName=<cluster-name> \ --set serviceAccount.create=false \ --set \ --set enableShield=false \ --set enableWaf=false \ --set enableWafv2=false \ --set \ -n kube-system

      The deployed chart does not receive security updates automatically. You need to manually upgrade to a newer chart when it becomes available.

    Kubernetes manifest
    1. Install cert-manager to inject certificate configuration into the webhooks.

      • Install on Kubernetes 1.16 or later.

        kubectl apply --validate=false -f
      • Install on Kubernetes 1.15.

        kubectl apply --validate=false -f
    2. Install the controller.

      1. Download the controller specification. For more information about the controller, see the documentation on GitHub.

        curl -o v2_1_3_full.yaml
      2. Make the following edits to the v2_1_3_full.yaml file:

        • Delete the ServiceAccount section from the specification. Doing so prevents the annotation with the IAM role from being overwritten when the controller is deployed and preserves the service account that you created in step 4 if you delete the controller.

        • Set the --cluster-name value to your Amazon EKS cluster name in the Deployment spec section.

        • Add the following parameters.

          --enable-shield=false --enable-waf=false --enable-wafv2=false

          Add the previous parameters under the existing --ingress-class=alb line of the following section.

          ... spec: containers: - args: - --cluster-name=your-cluster-name - --ingress-class=alb ...
      3. Apply the file.

        kubectl apply -f v2_1_3_full.yaml
  7. Verify that the controller is installed.

    kubectl get deployment -n kube-system aws-load-balancer-controller


    NAME READY UP-TO-DATE AVAILABLE AGE aws-load-balancer-controller 1/1 1 1 84s
  8. Before using the controller to provision AWS resources, your cluster must meet specific requirements. For more information, see Application load balancing on Amazon EKS and Network load balancing on Amazon EKS.