Using Existing Load Balancer Target Group
You can use an existing Load Balancer and its Target Group with the elb.existing settings. Example:
.ufo/config.rb
Ufo.configure do |config|
config.elb.existing.target_group = "arn:aws:elasticloadbalancing:us-west-2:111111111111:targetgroup/elb-d-Targe-12NCI2V1X5TBS/ed56e555b7e8d0db"
config.elb.existing.dns_name = "elb-dev-Elb-FOOAR4WRTPXKY-421647888.us-west-2.elb.amazonaws.com"
end
When using an existing Load Balancer, the other elb settings are ignored by UFO. This is because you’re “bringing your own” Load Balancer, it’s outside the control of UFO. You take on the responsibility of managing the ELB and its settings.
Reference
The table below covers each setting. Each option is configured in .ufo/config.rb with config.OPTION. The config. portion is not shown for conciseness. IE: logger.level vs config.logger.level.
| Name | Default | Description |
|---|---|---|
| elb.existing.dns_name | nil | For managed route53 record when using config.dns.domain option. Since UFO does not manage the ELB, this allows UFO to map the route53 dns record when needed. UFO infers the ELB dns name from the target group. However, in the case when the target group is associated with multiple ELBs, UFO cannot infer it and this setting is required. See: Existing Load Balancer Docs. |
| elb.existing.target_group | nil | Existing ELB target group. When using elb.existing.target_group the other elb settings are ignored since they only apply the ELB ufo manages. In the case of using an existing target group, the ELB is managed outside of UFO. You’re bring your own ELB. |