TLS

Envoy supports both TLS termination in listeners as well as TLS origination when making connections to upstream clusters. Support is sufficient for Envoy to perform standard edge proxy duties for modern web services as well as to initiate connections with external services that have advanced TLS requirements (TLS1.2, SNI, etc.). Envoy supports the following TLS features:

  • Configurable ciphers: Each TLS listener and client can specify the ciphers that it supports.
  • Client certificates: Upstream/client connections can present a client certificate in addition to server certificate verification.
  • Certificate verification and pinning: Certificate verification options include basic chain verification, subject name verification, and hash pinning.
  • Certificate revocation: Envoy can check peer certificates against a certificate revocation list (CRL) if one is provided.
  • ALPN: TLS listeners support ALPN. The HTTP connection manager uses this information (in addition to protocol inference) to determine whether a client is speaking HTTP/1.1 or HTTP/2.
  • SNI: SNI is supported for both server (listener) and client (upstream) connections.
  • Session resumption: Server connections support resuming previous sessions via TLS session tickets (see RFC 5077). Resumption can be performed across hot restarts and between parallel Envoy instances (typically useful in a front proxy configuration).

Underlying implementation

Currently Envoy is written to use BoringSSL as the TLS provider.

Enabling certificate verification

Certificate verification of both upstream and downstream connections is not enabled unless the validation context specifies one or more trusted authority certificates.

Example configuration

  1. static_resources:
  2.   listeners:
  3.   - name: listener_0
  4.     address: { socket_address: { address: 127.0.0.1, port_value: 10000 } }
  5.     filter_chains:
  6.     - filters:
  7.       - name: envoy.http_connection_manager
  8.         # ...
  9.       tls_context:
  10.         common_tls_context:
  11.           validation_context:
  12.             trusted_ca:
  13.               filename: /usr/local/my-client-ca.crt
  14.   clusters:
  15.   - name: some_service
  16.     connect_timeout: 0.25s
  17.     type: STATIC
  18.     lb_policy: ROUND_ROBIN
  19.     hosts: [{ socket_address: { address: 127.0.0.2, port_value: 1234 }}]
  20.     tls_context:
  21.       common_tls_context:
  22.         tls_certificates:
  23.           certificate_chain: { "filename": "/cert.crt" }
  24.           private_key: { "filename": "/cert.key" }
  25.         validation_context:
  26.           trusted_ca:
  27.             filename: /etc/ssl/certs/ca-certificates.crt

/etc/ssl/certs/ca-certificates.crt is the default path for the system CA bundle on Debian systems. This makes Envoy verify the server identity of 127.0.0.2:1234 in the same way as e.g. cURL does on standard Debian installations. Common paths for system CA bundles on Linux and BSD are

  • /etc/ssl/certs/ca-certificates.crt (Debian/Ubuntu/Gentoo etc.)
  • /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem (CentOS/RHEL 7)
  • /etc/pki/tls/certs/ca-bundle.crt (Fedora/RHEL 6)
  • /etc/ssl/ca-bundle.pem (OpenSUSE)
  • /usr/local/etc/ssl/cert.pem (FreeBSD)
  • /etc/ssl/cert.pem (OpenBSD)

See the reference for UpstreamTlsContexts and DownstreamTlsContexts for other TLS options.

Secret discovery service (SDS)

TLS certificates can be specified in the static resource or can be fetched remotely. Please see SDS for details.

Authentication filter

Envoy provides a network filter that performs TLS client authentication via principals fetched from a REST VPN service. This filter matches the presented client certificate hash against the principal list to determine whether the connection should be allowed or not. Optional IP white listing can also be configured. This functionality can be used to build edge proxy VPN support for web infrastructure.

Client TLS authentication filter configuration reference.