🛡️ Firewall Rules
Configure inbound and outbound traffic controls for your cloud infrastructure. Rules are evaluated by priority (lowest number first). Default action: DROP.
Configuration
ID: fw-8f4a2c91
Low Priority
High Priority (20)
Enable Logging
Stateful Tracking
Live Preview
rule_id: "fw-8f4a2c91"
name: "Allow-HTTPS-Inbound"
direction: "inbound"
action: "ALLOW"
protocol: "tcp"
port: 443
source: "0.0.0.0/0"
priority: 20
stateful: true
✅ Validation passed. Rule syntax is correct and ready for deployment.
Recent Traffic Events
2025-06-15 14:23:11
ALLOW
Src:
8.8.8.8 → Dst: 10.0.1.15:443 (TCP) | Rule: fw-8f4a2c912025-06-15 14:22:58
DROP
Src:
185.220.101.44 → Dst: 10.0.1.15:22 (TCP) | Rule: fw-3d91b2e4 | Reason: Botnet IP2025-06-15 14:21:33
ALLOW
Src:
203.0.113.42 → Dst: 10.0.1.15:22 (TCP) | Rule: fw-7c22a1f92025-06-15 14:20:12
DROP
Src:
45.95.169.3 → Dst: 10.0.1.15:3389 (TCP) | Rule: fw-default | Reason: Default Deny2025-06-15 14:19:45
ALLOW
Src:
10.0.1.15 → Dst: 13.107.42.14:443 (TCP) | Rule: fw-allow-outboundAPI & CLI Reference
Manage firewall rules programmatically using our REST API or Terraform provider. Rules follow a first-match-wins evaluation model.
# Create firewall rule via CloudNexus CLI
cxn firewall create \
--name "Allow-HTTPS-Inbound" \
--direction inbound \
--action allow \
--protocol tcp \
--port 443 \
--source 0.0.0.0/0 \
--priority 20 \
--stateful
# REST API Example
POST https://api.cloudnexus.io/v1/firewall/rules
{
"name": "Allow-HTTPS-Inbound",
"direction": "inbound",
"action": "allow",
"protocol": "tcp",
"port": "443",
"source_cidr": "0.0.0.0/0",
"priority": 20,
"enable_logging": true
}