Skip to main content


  • Config File Key: certificates (not yet settable using environmental variables)
  • Config File Key: certificate / certificate_key
  • Config File Key: certificate_file / certificate_key_file
  • Environmental Variable: CERTIFICATE / CERTIFICATE_KEY
  • Kubernetes: certificates
  • Type: array of relative file locations string
  • Type: base64 encoded string
  • Type: certificate relative file location string
  • Required (if insecure not set)

Certificates are the x509 public-key and private-key used to establish secure HTTP and gRPC connections. Any combination of the above can be used together, and are additive. You can also use any of these settings in conjunction with Autocert to get OCSP stapling.

Certificates loaded into Pomerium from these config values are used to attempt secure connections between end users and services, between Pomerium services, and to upstream endpoints.

For example, if specifying multiple certificates at once:

- cert: '$HOME/'
key: '$HOME/'
- cert: '$HOME/'
key: '$HOME/'
- cert: '$HOME/'
key: '$HOME/'

Or to set a single certificate and key covering multiple domains and/or a wildcard subdomain:

certificate_file: '$HOME/*'
certificate_key: '$HOME/**'

Note: Pomerium will check your system's trust/key store for valid certificates first. If your certificate solution imports into the system store, you don't need to also specify them with these configuration keys.