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
Security Group → Create Rule
AI-generatedSummary
Create an ingress or egress rule in the specified IONOS Cloud security group, using the selected protocol and any supplied rule properties.
Inputs
- Datacenter ID (required) — The ID of the datacenter containing the security group.
- Security Group ID (required) — The ID of the security group to add the rule to.
- Protocol (required) — Choose AH, ANY, ESP, GRE, ICMP, ICMPv6, TCP, UDP, or VRRP. Defaults to TCP; immutable after creation.
- Type (required) — Choose the traffic direction: Ingress or Egress. Defaults to Ingress.
- Rule Properties — Optional rule details: ICMP code and type, IP version, name, port range, source IP or MAC, and target IP. Port ranges default to 1–65535. The UI descriptions specify null values to allow all codes, ports, or addresses where applicable.
- Include Request Status — When enabled, include the asynchronous request tracking ID and status URL if returned by the API.
- Include Response Headers — When enabled, include response headers and status code, with the response body nested under
body. - Request Options — Optional batching, SSL certificate validation, proxy, and timeout settings.
Output shape
A single API response for the created rule.
The supplied source pack omits implementation bodies, so the exact response fields and runtime handling of optional properties cannot be confirmed. Enabling Include Response Headers wraps the response body alongside headers and statusCode.