Actions140
- Application Load Balancer Actions
- Contract Actions
- Datacenter Actions
- Firewall Rule Actions
- Image Actions
- IP Block Actions
- Kubernetes Cluster Actions
- LAN Actions
- Load Balancer Actions
- Location Actions
- NAT Gateway Actions
- Network Load Balancer Actions
- NIC Actions
- Node Pool Actions
- Private Cross-Connect Actions
- Request Actions
- Security Group Actions
- Server Actions
- Snapshot Actions
- Target Group Actions
- Volume Actions
Application Load Balancer → Create Forwarding Rule
AI-generatedSummary
Creates an HTTP forwarding rule on the specified IONOS Cloud Application Load Balancer in a datacenter. Configure its listener, protocol, and optional HTTP routing rules, certificates, and client timeout; routing rules can forward requests to a target group, return a static response, or redirect.
Inputs
- Datacenter ID (required) — ID of the datacenter containing the Application Load Balancer.
- Application Load Balancer ID (required) — ID of the load balancer to add the forwarding rule to.
- Forwarding Rule Properties — Optional rule settings: client timeout in milliseconds (default 50000), HTTP rules, listener IP, listener port (default 8080; valid range 1–65535), name, protocol (HTTP), and comma-separated server certificate UUIDs. HTTP rules are processed in order, except FORWARD rules, which are processed last. Rule fields include action type (FORWARD, STATIC, or REDIRECT), name, target group UUID, redirect location and query handling, or static response content type, message, and status code.
- Include Request Status — When enabled, includes the request tracking ID and status URL from the API response for the asynchronous operation.
- Include Response Headers — When enabled, includes response headers and status code, with the response body nested under a body key.
- Request Options — Optional batching, SSL certificate validation, proxy, and request timeout settings.
Output shape
A single API response per input item.
By default, output contains the response body. Enabling Include Response Headers wraps it under body and adds headers and statusCode; enabling Include Request Status adds request tracking details when provided by the API. The supplied source pack omits operation implementation bodies, so the exact response shape cannot be confirmed from source.