Chef Automate ALB -> ELB #39
Description
The Chef Automate configuration in terraform for AWS makes use of an application load balancer (ALB) to act as an endpoint for a dynamically generated route53 domain. While this works well for forwarding web requests, it presents challenges for forwarding non-web TCP requests, as with the event stream configuration needed for the EAS dashboard.
Since TLS is not currently supported in the EAS event stream, this is currently addressed by pointing supervisors to the Automate Server's IP address directly over port 4222. This works, but should be considered a stopgap solution.
Long term, we want to be able to point things to the proper hostname, as with data collection. Per a conversation with @jvogt, this can be accomplished by using an elastic load balancer (ELB) in favor of the current ALB setup.
Here is a reference from one of his repos to help guide development on this change: https://github.com/jvogt/2019-demo-terraform/blob/4901d9a10f6be198062a9b00e5984e8327e4771a/automate/aws/chef_automate_elb.tf