Before you can teach your client to speak TLS, you will need a certificate issued by a trusted certificate authority (CA). If your organization already runs its own CA and you have a private key and certificate for your Prometheus client, along with your CA's root certificate, you can skip to the next step.
To request a certificate from your CA using the
step CLI, bootstrap your CA with
step ca bootstrap and run the following command (sub the client name for the actual name / DNS name of your Prometheus client).
$ step ca certificate "myuser" client.crt client.key
Your certificate and private key will be saved in
Request a copy of your CA root certificate, which will be used to make sure each application can trust certificates presented by other applications.
$ step ca root ca.crt
Your certificate will be saved in
Now, we need only to configure our Prometheus client to make authenticated requests using our certificate and private key. The CA root certificate will be used to verify that the client can trust the certificate presented by the server.
Add the following job configuration block to your
prometheus.yml to authenticate as a client to your targets:
- job_name: 'node'
# Prometheus will check that the node_exporter presents a certificate
# signed by this ca.
# The cert and key are presented to node_exporter to authenticate
# Prometheus as a client.
- targets: ['myserver.internal.net:443']
Reload Prometheus, and confirm that the Prometheus dashboard shows your target endpoints as "UP"—and using the
step-ca issues certificates with a 24 hour expiration. Short-lived certificates have many benefits but also require that you renew your certificates each day before they expire. How you renew certificates is often dependent on how you deploy your application. See the
step-ca certificate lifecycle management docs for more information.
All documentation content from the Hello mTLS project is licensed under Creative Commons Attribution 4.0 International (CC BY 4.0).