Create listener in ELB if it doesn't exists

[kiddouk]

Letslambda will fail to update an HTTPS listener if it doesn't exists already.

This should be created.

[aureq]

There's few issues with this. Is it LetsLambda responsibility to create the listener? Which type of Listener should be defined (HTTPS vs SSL), when the traffic should be directed to (backend HTTP or HTTPS), and which SSL policy should be deployed?

[kiddouk]

It is not letslambda responsibility per say but for now, if you try to create an ELB with an HTTPS listener but without a certificate, cloudformation fails, meaning that to use letslambda, you need to have an HTTPS listener installed that will get updated. Otherwise, letslambda fails with "No such listener" error.

I think that we could go about it a few options to configure the ELB properly if it is missing the right listener.

Other way to proceed, triggering an SNS when the certificate is created so that "something" would modify the ELB ... not optimal IMHO.