You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 19, 2022. It is now read-only.
milosgajdos
changed the title
ELB resource should have an option for a communication protocol
ELB resource should have options for SSL certs and communication protocol
Feb 19, 2015
Personally - I don't think we should put SSL certs on the ELB as it makes the process of updating the certs harder (it's easier to manage via salt) - also as we will be running nginx on each docker host, it's not extra overhead to run SSL there as well
At the moment by default
bootstrap-cfn
creates TCP based ELBs.There should be an option of a communication protocol. In practice we mostly use HTTP/HTTPs Load Balancers, anyways.
On top of this, you should have an option to specify a path to SSL certificates and keys if you need to create TCP(SSL)/HTTPS ELB.
The text was updated successfully, but these errors were encountered: