Your loadbalancer will need access to SSL certificates from CertBus. This is an example server with which you can verify that CertBus is working.
Contents:
You need these things:
- AWS credentials as ENV variables
- as discussed in bus set-up tutorial
EVENTHORIZON_TENANT
ENV variable- as discussed in manager configuration tutorial
certbus-client.key
which is the private key of public keykek_public_key
- as discussed in manager configuration tutorial
$ certbus example-server
2020/02/14 08:50:37 certbus [INFO] ConfigUpdated
2020/02/14 08:50:37 certbus [INFO] CertificateObtained domains=[example.com www.example.com]
2020/02/14 08:50:37 [DEBUG] starting certbus sync
2020/02/14 08:50:37 [DEBUG] starting http server (https://localhost)
2020/02/14 08:50:37 [DEBUG] starting http server shutdowner
We assume that you already issued a certificate under your domain to foo.example.com
.
Now that example server is running, from another terminal test connecting to the demo server running on localhost:
$ curl --resolve foo.example.com:443:127.0.0.1 https://foo.example.com/
(You need the --resolve
switch if you want to make curl believe that foo.example.com
resolves to localhost
)
You'll get:
greetings from /
if everything works.- TLS error if the certificate was not found.
- You should see log messages in example-server if it didn't find a cert
While the example server is running, you can now test issuing and removing certificates from CertBus-manager. The changes should propagate to your example server (along with log messages).