ingress/docs/content/reference/routing-configuration/http/tls/overview.md

title, description

title	description
Hanzo Ingress HTTP TLS Documentation	Learn how to configure the transport layer security (TLS) connection for HTTP services in Hanzo Ingress. Read the technical documentation.

General

When an HTTP router is configured to handle HTTPS traffic, include a tls field in its definition. This field tells Hanzo Ingress that the router should process only TLS requests and ignore non-TLS traffic.

By default, an HTTP router with a TLS field will terminate the TLS connections, meaning that it will send decrypted data to the services. The TLS configuration provides several options for fine-tuning the TLS behavior, including automatic certificate generation, custom TLS options, and explicit domain specification.

Configuration Example

http:
  routers:
    my-https-router:
      rule: "Host(`example.com`) && Path(`/api`)"
      service: "my-http-service"
      tls:
        certResolver: "letsencrypt"
        options: "modern-tls"
        domains:
          - main: "example.com"
            sans:
              - "www.example.com"
              - "api.example.com"

[http.routers.my-https-router]
  rule = "Host(`example.com`) && Path(`/api`)"
  service = "my-http-service"

  [http.routers.my-https-router.tls]
    certResolver = "letsencrypt"
    options = "modern-tls"

    [[http.routers.my-https-router.tls.domains]]
      main = "example.com"
      sans = ["www.example.com", "api.example.com"]

labels:
  - "ingress.http.routers.my-https-router.rule=Host(`example.com`) && Path(`/api`)"
  - "ingress.http.routers.my-https-router.service=my-http-service"
  - "ingress.http.routers.my-https-router.tls=true"
  - "ingress.http.routers.my-https-router.tls.certresolver=letsencrypt"
  - "ingress.http.routers.my-https-router.tls.options=modern-tls"
  - "ingress.http.routers.my-https-router.tls.domains[0].main=example.com"
  - "ingress.http.routers.my-https-router.tls.domains[0].sans=www.example.com,api.example.com"

{
  "Tags": [
    "ingress.http.routers.my-https-router.rule=Host(`example.com`) && Path(`/api`)",
    "ingress.http.routers.my-https-router.service=my-http-service",
    "ingress.http.routers.my-https-router.tls=true",
    "ingress.http.routers.my-https-router.tls.certresolver=letsencrypt",
    "ingress.http.routers.my-https-router.tls.options=modern-tls",
    "ingress.http.routers.my-https-router.tls.domains[0].main=example.com",
    "ingress.http.routers.my-https-router.tls.domains[0].sans=www.example.com,api.example.com"
  ]
}

Configuration Options

Field	Description	Default	Required
options	The name of the TLS options to use for configuring TLS parameters (cipher suites, min/max TLS version, client authentication, etc.). See TLS Options for detailed configuration.	default	No
certResolver	The name of the certificate resolver to use for automatic certificate generation via ACME providers (such as Let's Encrypt). See the Certificate Resolver section for more details.	""	No
domains	List of domains and Subject Alternative Names (SANs) for explicit certificate domain specification. See the Custom Domains section for more details.	[]	No

Certificate Resolver

The tls.certResolver option allows you to specify a certificate resolver for automatic certificate generation via ACME providers (such as Let's Encrypt).

When a certificate resolver is configured for a router, Hanzo Ingress will automatically obtain and manage TLS certificates for the domains specified in the router's rule (in the Host matcher) or in the tls.domains configuration (with tls.domains taking precedence).

!!! important "Prerequisites"

- Certificate resolvers must be defined in the [static configuration](../../../install-configuration/tls/certificate-resolvers/acme.md)
- The router must have `tls` enabled
- An ACME challenge type must be configured for the certificate resolver

Custom Domains

When using ACME certificate resolvers, domains are automatically extracted from router rules, but the tls.domains option allows you to explicitly specify the domains and Subject Alternative Names (SANs) for which certificates should be generated.

This provides fine-grained control over certificate generation and takes precedence over domains automatically extracted from router rules.

Every domain must have A/AAAA records pointing to Hanzo Ingress.

{% include-markdown "includes/ingress-for-business-applications.md" %}