A tls listener ends TLS at the load balancer, with TLS 1.2 or 1.3, and sends plain TCP to its
targets inside your VPC. It takes a certificate (crt_…) that’s been issued in the
project. An https listener ends TLS the same way and then routes each request.
ezgh lb listeners create lbr_4k2m9x0a7qpe --protocol tls --port 443 \
--target-group tgp_7t3n1v8c2wzd --certificate crt_8s4f2k9d1mzq- A certificate that hasn’t been issued is refused:
409 certificate_not_issued. - You need
certificates.certificates.useon the certificate. - Renewals reach the listener by themselves.
- A certificate that expires, or can’t be delivered, shows on the load balancer as a
lastChangeofnot_applied, with the reason.
Several domains on one listener
--additional-certificate (additionalCertificates, at most 24) adds certificates to a tls or https
listener. A client gets the one whose names cover the name it asks for (SNI); a client that asks for none
of them, or sends no name, gets the listener’s own --certificate. Each renews by itself.
ezgh lb listeners update lbr_4k2m9x0a7qpe lsn_1b8c4d6f0gkm \
--additional-certificate crt_5w1y7a3c9edg --additional-certificate crt_0z4x8v2n6bprThe list replaces the one before; --no-additional-certificates empties it.
Changing a certificate
To change a listener’s certificate:
ezgh lb listeners update lbr_4k2m9x0a7qpe lsn_1b8c4d6f0gkm --certificate crt_2t6h9j3k5lnp