Actions34
- LAN Actions
- NIC Actions
- Firewall Rule Actions
- IP Block Actions
- NAT Gateway Actions
- NAT Gateway Rule Actions
- Flow Log Actions
Flow Log → Create
AI-generatedSummary
Create a flow log attached to a specified network resource.
Inputs
- flowLogParent (required) — The type of resource the flow log is attached to. Options: NIC (flow log for a network interface) or NAT Gateway (flow log for a NAT gateway). Default: NIC.
- datacenterId (required) — The unique ID of the datacenter where the resource exists.
- serverId (required) — The unique ID of the server. Required when flowLogParent is NIC.
- nicId (required) — The unique ID of the NIC. Required when flowLogParent is NIC.
- natGatewayId (required) — The unique ID of the NAT gateway. Required when flowLogParent is NAT gateway.
- flowLogName (required) — The name of the flow log.
- action (required) — The traffic action to log. Options: ACCEPTED, REJECTED, ALL. Default: ALL.
- direction (required) — The traffic direction to log. Options: INGRESS, EGRESS, BIDIRECTIONAL. Default: BIDIRECTIONAL.
- bucket (required) — The S3 bucket name where logs will be stored.
- additionalFields — Additional fields to extend the flow log configuration (optional).
Output shape
The IONOS API response containing the created flow log's details, returned via n8n's main output after POSTing to the appropriate endpoint (servers/{serverId}/nics/{nicId}/flowlogs or natgateways/{natGatewayId}/flowlogs).
The operation constructs the API endpoint based on flowLogParent (NIC or NAT gateway), then sends a POST with {properties: {name, action, direction, bucket}}. All required parameters (flowLogParent, datacenterId, serverId or natGatewayId, nicId or natGatewayId, flowLogName, action, direction, bucket) must be provided; additionalFields are optional.