HTTPS and authentication

Prometheus supports basic authentication and TLS. This is experimental and might change in the future.

To specify which web configuration file to load, use the --web.config.file flag.

The file is written in YAML format, defined by the scheme described below. Brackets indicate that a parameter is optional. For non-list parameters the value is set to the specified default.

The file is read upon every http request, such as any change in the configuration and the certificates is picked up immediately.

Generic placeholders are defined as follows:

  • <boolean>: a boolean that can take the values true or false
  • <filename>: a valid path in the current working directory
  • <secret>: a regular string that is a secret, such as a password
  • <string>: a regular string

A valid example file can be found here.

  1. tls_server_config:
  2. # Certificate and key files for server to use to authenticate to client.
  3. cert_file: <filename>
  4. key_file: <filename>
  5. # Server policy for client authentication. Maps to ClientAuth Policies.
  6. # For more detail on clientAuth options:
  7. # https://golang.org/pkg/crypto/tls/#ClientAuthType
  8. #
  9. # NOTE: If you want to enable client authentication, you need to use
  10. # RequireAndVerifyClientCert. Other values are insecure.
  11. [ client_auth_type: <string> | default = "NoClientCert" ]
  12. # CA certificate for client certificate authentication to the server.
  13. [ client_ca_file: <filename> ]
  14. # Minimum TLS version that is acceptable.
  15. [ min_version: <string> | default = "TLS12" ]
  16. # Maximum TLS version that is acceptable.
  17. [ max_version: <string> | default = "TLS13" ]
  18. # List of supported cipher suites for TLS versions up to TLS 1.2. If empty,
  19. # Go default cipher suites are used. Available cipher suites are documented
  20. # in the go documentation:
  21. # https://golang.org/pkg/crypto/tls/#pkg-constants
  22. [ cipher_suites:
  23. [ - <string> ] ]
  24. # prefer_server_cipher_suites controls whether the server selects the
  25. # client's most preferred ciphersuite, or the server's most preferred
  26. # ciphersuite. If true then the server's preference, as expressed in
  27. # the order of elements in cipher_suites, is used.
  28. [ prefer_server_cipher_suites: <bool> | default = true ]
  29. # Elliptic curves that will be used in an ECDHE handshake, in preference
  30. # order. Available curves are documented in the go documentation:
  31. # https://golang.org/pkg/crypto/tls/#CurveID
  32. [ curve_preferences:
  33. [ - <string> ] ]
  34. http_server_config:
  35. # Enable HTTP/2 support. Note that HTTP/2 is only supported with TLS.
  36. # This can not be changed on the fly.
  37. [ http2: <boolean> | default = true ]
  38. # List of headers that can be added to HTTP responses.
  39. [ headers:
  40. # Set the Content-Security-Policy header to HTTP responses.
  41. # Unset if blank.
  42. [ Content-Security-Policy: <string> ]
  43. # Set the X-Frame-Options header to HTTP responses.
  44. # Unset if blank. Accepted values are deny and sameorigin.
  45. # https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Frame-Options
  46. [ X-Frame-Options: <string> ]
  47. # Set the X-Content-Type-Options header to HTTP responses.
  48. # Unset if blank. Accepted value is nosniff.
  49. # https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Content-Type-Options
  50. [ X-Content-Type-Options: <string> ]
  51. # Set the X-XSS-Protection header to all responses.
  52. # Unset if blank. Accepted value is nosniff.
  53. # https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-XSS-Protection
  54. [ X-XSS-Protection: <string> ]
  55. # Set the Strict-Transport-Security header to HTTP responses.
  56. # Unset if blank.
  57. # Please make sure that you use this with care as this header might force
  58. # browsers to load Prometheus and the other applications hosted on the same
  59. # domain and subdomains over HTTPS.
  60. # https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Strict-Transport-Security
  61. [ Strict-Transport-Security: <string> ] ]
  62. # Usernames and hashed passwords that have full access to the web
  63. # server via basic authentication. If empty, no basic authentication is
  64. # required. Passwords are hashed with bcrypt.
  65. basic_auth_users:
  66. [ <string>: <secret> ... ]