Skip to content

AWS Load Balancer Controller

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

  • 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.

For more information about AWS Load Balancer Controller please see the official documentation.


enable_aws_load_balancer_controller = true

You can optionally customize the Helm chart that deploys aws-lb-ingress-controller via the following configuration.

  enable_aws_load_balancer_controller = true
  # Optional  
  aws_load_balancer_controller_helm_config = {
    name                       = "aws-load-balancer-controller"
    chart                      = "aws-load-balancer-controller"
    repository                 = ""
    version                    = "1.3.1"
    namespace                  = "kube-system"
    values = [templatefile("${path.module}/values.yaml", {})]

To validate that controller is running, ensure that controller deployment is in RUNNING state:

# Assuming controller is installed in kube-system namespace
$ kubectl get deployments -n kube-system
NAME                                                       READY   UP-TO-DATE   AVAILABLE   AGE
aws-load-balancer-controller                               2/2     2            2           3m58s

AWS Service annotations for LB Ingress Controller

Here is the link to get the AWS ELB service annotations for LB Ingress controller.

GitOps Configuration

The following properties are made available for use when managing the add-on via GitOps.

awsLoadBalancerController = {
  enable             = true
  serviceAccountName = "<service_account_name>"