Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

How do I attach an elastic IP upon creation of a network load balancer with Terraform?

I'm attempting to associate my elastic IP address to a newly created network balancer using Terraform. I see no option in the aws_lb documentation for adding an elastic IP like one is able to do in the AWS console. The difficulty is that you have to associate the elastic IP upon creation of NLB.

EDIT: They now have made an explicit example on their documentation!

like image 700
Steve Avatar asked Apr 10 '18 19:04

Steve


People also ask

Can we attach elastic IP to load balancer?

Select Use an Elastic IP address from the dropdown list to assign to your Network Load Balancer. After you specify the Elastic IP addresses for the Network Load Balancer, complete the remaining steps for creating a Network Load Balancer.

How do you allocate an elastic IP address?

To allocate an Elastic IP address Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/ . In the navigation pane, choose Network & Security, Elastic IPs. Choose Allocate Elastic IP address.


2 Answers

The aws_lb resource has a subnet_mapping block which allows you to specify an Elastic IP per subnet that the network load balancer exists in.

An absolutely minimal example looks something like this:

resource "aws_eip" "lb" {
  vpc = true
}

resource "aws_lb" "network" {
  name               = "test-lb-tf"
  load_balancer_type = "network"

  subnet_mapping {
    subnet_id     = "${var.subnet_id}"
    allocation_id = "${aws_eip.lb.id}"
  }
}

Obviously you'll probably want to run the load balancer in multiple subnets so you'd probably use something like this:

variable "vpc" {}

data "aws_vpc" "selected" {
  tags {
    Name = "${var.vpc}"
  }
}

data "aws_subnet_ids" "public" {
  vpc_id = "${data.aws_vpc.selected.id}"

  tags {
    Tier = "public"
  }
}

resource "aws_eip" "lb" {
  count = "${length(data.aws_subnet_ids.public)}"
  vpc   = true
}

resource "aws_lb" "network" {
  name               = "test-lb-tf"
  internal           = false
  load_balancer_type = "network"

  subnet_mapping {
    subnet_id     = "${data.aws_subnet_ids.public.ids[0]}"
    allocation_id = "${aws_eip.lb.id[0]}"
  }

  subnet_mapping {
    subnet_id     = "${data.aws_subnet_ids.public.ids[1]}"
    allocation_id = "${aws_eip.lb.id[1]}"
  }

  subnet_mapping {
    subnet_id     = "${data.aws_subnet_ids.public.ids[2]}"
    allocation_id = "${aws_eip.lb.id[2]}"
  }
}

The above assumes you have tagged your VPC with a Name tag and your subnets with a Tier tag that in this case uses public as the value for any external facing subnets. It then creates an elastic IP address for each of the public subnets a network load balancer in each of the public subnets, attaching an elastic IP for each of them.

like image 192
ydaetskcoR Avatar answered Oct 22 '22 05:10

ydaetskcoR


The above answer is correct, however it can now be simplified using dynamic blocks available in Terraform 0.12. This has the advantage of working in vpcs with more or less subnets.

resource "aws_lb" "network" {
  name               = "test-lb-tf"
  internal           = false
  load_balancer_type = "network"

  dynamic "subnet_mapping" {
    for_each = data.aws.subnet_ids.public_ids
    content {
      subnet_id     = subnet_mapping.value
      allocation_id = aws_eip.lb.id[subnet_mapping.key].allocation_id
    }
  }
}
like image 21
Nick Palmer Avatar answered Oct 22 '22 07:10

Nick Palmer