What Is It?
Managed Application Load Balancer (ALB) distributes HTTP/HTTPS traffic across multiple targets at OSI Layer 7 (application layer). ALB inspects full HTTP requests including method, headers, host, path, query strings, cookies, and source IP to make intelligent routing decisions. The service performs TLS termination at the listener, supports path-based routing, and provides health checks to ensure traffic only reaches healthy targets.
Quick Facts
| Aspect | Details |
|---|---|
| Type | Layer 7 (application layer) load balancer |
| Protocols | HTTP, HTTPS (with TLS termination) |
| IP Types | Public (reserved IPv4) or Private (automatic) |
| Routing Methods | Host, path, method, header, query, cookie, source IP |
| HTTP Actions | Forward, Redirect, Static Response |
| Health Checks | TCP or HTTP |
| Algorithms | Round Robin (default), Least Connections, Random, Source IP |
| Management | DCD, Cloud API, DevOps Tools |
| Logs | Flow logs to an IONOS Object Storage bucket; access logs to the Logging Service (newly created ALBs in non-US data centers only, central logging required) |
What You Can Do
Layer 7 Routing
Route traffic based on HTTP request attributes including host, path, method, headers, query strings, cookies, and source IP. Create complex routing logic with multiple conditions per forwarding rule.
TLS Termination
Attach SSL certificates to the forwarding rules for HTTPS termination at the ALB. Inbound HTTPS traffic is decrypted at the ALB (TLS offloading), and the target group forwards it to the targets over HTTP.
With Server Name Indication (SNI), several secure websites can share one public IP with their own certificates. Certificates are imported through the Certificate Manager and must use RSA keys.
Path-Based Routing
Direct requests to different target groups based on URL paths. Route /api/ to API servers, /static/ to content servers, and other paths to application servers.
Host-Based Routing
Route different hostnames to different target groups. Serve app.example.com and admin.example.com from the same ALB using different backends.
HTTP Redirects
Configure redirect rules to force HTTP to HTTPS, redirect old URLs to new locations, or implement custom redirect logic based on request attributes.
Fixed Response Rules
Return static HTTP responses for specific requests. Useful for health check endpoints, maintenance pages, or simple responses without backend targets.
Forwarding Rules with Priority
Create multiple forwarding rules per listener with priority ordering. Rules are evaluated in priority order with a default rule as fallback for unmatched requests.
Health Checks
Configure HTTP or TCP health checks per target group. ALB periodically sends requests to registered targets and removes unhealthy instances from rotation automatically.
Public and Private Listeners
Create public listeners using reserved IPv4 addresses for external traffic, or private listeners with automatic private IPs for internal traffic.
Client IP Preservation
Preserve the client source IP in request headers or with Proxy Protocol (v1, v2, v2ssl) on the target, and set a weight from 1 to 256 per target to control its share of traffic.
WebSocket and gRPC Support
Support WebSocket connections and gRPC protocols. For gRPC, set the target group protocol to HTTP and the protocol version to HTTP2. Do not configure an HTTP health check when WebSocket or gRPC support is intended; TCP health checks are allowed for WebSocket targets.
Best For
| Scenario | Why It Fits |
|---|---|
| Microservices architectures | Route different paths or hosts to different service backends |
| HTTP/HTTPS applications | Layer 7 inspection and routing for web applications |
| SSL/TLS termination | Offload certificate management and decryption from backend servers |
| Complex routing logic | Multiple conditions per rule (host + path + header combinations) |
| API gateways | Route API requests based on path, method, or headers |
| Multi-tenant applications | Host-based routing to separate tenant backends |
| HTTP to HTTPS redirect | Force secure connections with redirect rules |
Key Considerations
Billing & Costs
- Main billing: Per forwarding rule per hour (no separate per-ALB-instance fee); a minimum charge equal to one rule applies even if none are configured.
- Additional costs: Public IP address reservation (if using public listeners)
- Per Forwarding Rule: The first 5 forwarding rules are billed at 0,02 EUR/hour each, additional rules at 0,01 EUR/hour each, with a minimum charge equivalent to one rule
- Egress Traffic not included in the ALB price: Egress traffic is billed separately and will come on top of the ALB price
Limitations
- Source NAT (SNAT) not supported (targets cannot initiate connections through ALB)
- TLS terminates at the ALB (TLS offloading); target groups forward traffic to the targets over HTTP
- Public listeners require reserved public IPv4 address
- Health checks defined per target group, not per forwarding rule
- Up to 10 listeners per ALB
- Up to 5 ALBs per contract (can be raised through the IONOS Cloud Support Team)
- IPv6 support has limitations
- Weekly maintenance window every Monday 02:00 to 04:00 local data center time, with a possible service interruption of up to 5 seconds
Management Options
- Data Center Designer (DCD)
- Cloud API
- Configure listeners, forwarding rules, target groups, and health checks
- Access logging via central logging, viewed in a dedicated Grafana instance (newly created ALBs in non-US data centers only; enabling central logging incurs additional costs).
- Flow Logs can be written to a user-owned IONOS Object Storage bucket.