Skip to content
This repository has been archived by the owner on Jan 19, 2022. It is now read-only.

ELB resource should have options for SSL certs and communication protocol #4

Closed
milosgajdos opened this issue Feb 19, 2015 · 2 comments

Comments

@milosgajdos
Copy link
Contributor

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.

@milosgajdos milosgajdos reopened this Feb 19, 2015
@milosgajdos 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
@stuartornum
Copy link
Contributor

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

@milosgajdos
Copy link
Contributor Author

Right. This is a valid point. I'm closing this issue.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants