aws-static-ip-nlb-alb
Adaptavist/aws-static-ip-nlb-alb/module
Overview At the moment, AWS ALBs can't be associated with elastic IPs. This module provides a way to resolve this problem by implementing the solution based on the following article: https://aws.amazon.com/blogs/networking-and-content-delivery/using-static-ip-addresses-for-application-load-balancers/ Main resources created - Public facing NLB with a set of elastic IPs, one for each public subnet - Internal ALB - S3 access log bucket for both LBs - Lambda function that is responsible for the attachment of ALB IPs to the NLB target group - S3 bucket and cloudwatch resources that accompany the lambda function above Inputs | Name | Description | Type | Default | Required | |------|-------------|------|---------|:--------:| | alb\_sg\_id | ALB security group id | string | n/a | yes | | deletion
| Name | Type | Description | Default |
|---|---|---|---|
| alb_sg_id | string | ALB security group id | |
| deletion_protection_enabled | bool | Indicates if load balancers can be deleted | |
| vpc_id | string | VPC that will host this solution | |
| public_subnets | list(string) | List of public subnet ids | |
| tags | map(string) | Map of tags that should be applied to all resources | |
| name | string | Solution name | |
| private_subnets | list(string) | List of private subnet ids | |
| max_lookup_per_invocation | number | The max times of DNS look per invocation. | 50 |
| invocations_before_deregistration | number | The number of required Invocations before an IP address is de-registered. | 3 |
external_nlb_dns_nameexternal_nlb_zone_idexternal_nlb_arninternal_alb_arninternal_alb_dns_nameinternal_alb_zone_id