Skip to content

This module helps you to update the private IP addresses as registered target in the internal NLB and of course as Route53 entry, if you have a chained setup of NLB's in your private subnets. The problem it would solve is, that the private IP's can change anytime.

License

Notifications You must be signed in to change notification settings

elastic2ls-com/terraform-aws-internal-nlb-ip-update

Repository files navigation

Terraform module to update private ip addresses of internal nlb targets

 

License Status Sponsor Contact Terraform Registry

This module helps you to update the private IP addresses as registered target in the internal NLB and of course as Route53 entry, if you have a chained setup of NLB's in your private subnets. The problem it would solve is, that the private IP's can change anytime.

  • two lambda functions
  • a sns topic
  • a cloudwatch event

Lambdas to update private IP

dns

Does an update of an A record with the private ip adresses of an ALB.

ip_update

Does an update of the nlb target group with the private ip adresses of the ALB.

Sample Usage

This module requires 5 arguments.

  • stage the stage name will be used in different places.
  • alb_description_name the description of the internal NLB which private ip address you want to gather.
  • zone_id the id of the route53 zone which need to be updated.
  • nlb_tg_arn the arn of the target loadbalancer, which needs to be updated.
  • intra_dns_name the name of the internal domain
module "terraform-aws-internal-nlb-ip-update" {
source = "git@github.com:elastic2ls/terraform-aws-internal-nlb-ip-update.git"

  stage                 = var.stage
  alb_description_name  = var.alb_description_name
  zone_id               = var.zone_id
  nlb_tg_arn            = var.nlb_tg_arn
  intra_dns_name        = var.intra_dns_name
}

The module can also be found in the Terraform Registry https://registry.terraform.io/modules/elastic2ls-com/internal-nlb-ip-update/aws/latest.

About

This module helps you to update the private IP addresses as registered target in the internal NLB and of course as Route53 entry, if you have a chained setup of NLB's in your private subnets. The problem it would solve is, that the private IP's can change anytime.

Resources

License

Stars

Watchers

Forks

Packages

No packages published