What Load balancing does not support

Features load balancers do not have, so you can plan around them.

Last updated 18 November 2026View as Markdown
  • Changing the type, algorithm, region, VPC or scheme after creation.
  • Joining a VPC from the console (lb11–lb31): use the CLI, API or Terraform at creation.
  • Changing a service in the console. Changing a service's protocol, ports or certificate at all: remove the service and add it again.
  • A certificate issued by Deutsche Cloud for a name outside your Deutsche Cloud hosted zones.
  • Renewing or replacing an uploaded certificate in place.
  • Re-encrypting to the targets: an https service sends plain HTTP to them.
  • An instance target in another region than the load balancer's (an IP address target is not checked for its region).
  • Target health from the health check on lb11–lb31: their target status stays healthy.
  • On lb11–lb31: host and path rules, a web ACL, live numbers, an access log, a separate health-check port, closeOnUnhealthy.
  • On application: tcp, ports other than 80 and 443, targets in a VPC, PROXY protocol, a separate health-check port; rules that redirect, rewrite the path or answer by themselves; a health check per target group.
  • On dedicated: rules, target groups and a web ACL; a certificate issued for domains and the HTTP-to-HTTPS redirect. The API accepts both, but an https service with domains is never served, and port 80 does not redirect. Use an uploaded certificate without the redirect and, for port 80, an http service.
Did this page help you?