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 Flow Log
AI-generatedSummary
Creates a flow log for an Application Load Balancer in the specified datacenter, using the supplied flow log properties.
Inputs
- Datacenter ID (required) — ID of the datacenter containing the load balancer.
- Application Load Balancer ID (required) — ID of the load balancer to create the flow log for.
- Flow Log Properties — Optional flow log settings: name, traffic action pattern (ACCEPTED, REJECTED, or ALL; defaults to ALL), traffic direction (INGRESS, EGRESS, or BIDIRECTIONAL; defaults to BIDIRECTIONAL), and the name of an existing IONOS Cloud Object Storage bucket.
- Include Request Status — When enabled, includes the async request tracking ID and status URL in the output.
- Include Response Headers — When enabled, includes the HTTP headers and status code; the response body is nested under
body. - Request Options — Optional request settings for batching, SSL certificate validation, proxy, and timeout.
Output shape
A single API response item describing the created flow log.
The provided source pack contains no operation implementation bodies, so the exact response fields and asynchronous behavior cannot be confirmed. Enabling response headers changes the output to include
body,headers, andstatusCode; request tracking output is optional.