Skip to main content

​
Summary

​
Configuration (typical)

  • Name and region — Scope the rule set to a cloud region where your VPC/network lives.
  • Rules — Structured as inbound and outbound arrays; each rule can use a preset protocol (for example HTTP on port 80, HTTPS on 443, MySQL on 3306) or custom TCP/UDP with an explicit port, plus ICMP or All where supported.
  • Source / destination — Often Anywhere or a custom CIDR for fine-grained access.
The UI groups protocols into categories (Web, Remote access, Database, Network services, DevOps, and so on) so you do not have to remember port numbers for common services.

​
Canvas and connections

  • Attach firewalls to servers, scalable servers, or other network-facing resources your deployment allows—so traffic paths reflect real security boundaries.

​
Operations

  • Sync refreshes rule state from the provider when supported.
  • Delete removes the firewall resource and associated cloud objects per API behavior.
API: API documentation → Firewalls, Resources, Resource connections. ← Resource types hub