ALB configuration

An Application Load Balancer is configured through a few platform resources: an HTTPProxy for hostnames, routes, and origins, a TrafficProtectionPolicy for the web application firewall, and an optional SecurityPolicy for authentication. For how they fit together, see What an ALB is made of. In the Cloud Portal, a load balancer’s Configuration tab gathers its settings in one place: general details, custom hostnames, the backend pool, TLS and certificates, security and the web application firewall, and access control.

The Configuration tab of a load balancer with sections for General, Custom Hostnames, Backend pool, TLS and Certificates, Security and WAF in Enforce mode, and Access Control — A load balancer's settings in the Cloud Portal

To configure	See
The web application firewall	Web application firewall
A wildcard hostname, such as `*.example.com`	Wildcard hostnames
Routes, redirects, rewrites, and headers on the proxy	HTTPProxy
A custom domain with `datumctl`	Serve traffic on your own domain
Several origins and path routes with `datumctl`	Send paths to different origins
Origin weights, the load balancing algorithm, and passive health checks	Load balancing and health checks
Basic or OIDC authentication	Authentication
Failover between a primary and a fallback origin	Failover

Introduction

Explore