Cloud Firewall - Create, Configure Rules, Manage Servers, and Destroy

TL;DR - In EasyCloudify™, Cloud Firewall works at the network layer. You create a firewall once, then apply it to specific servers and/or tags. Tag targeting is the fastest way to secure entire groups of servers.

What Cloud Firewall Protects

Cloud Firewall controls traffic before it reaches your server services.

• Inbound rules define what traffic is allowed into servers.
• Outbound rules define what traffic is allowed to leave servers.
• You can target protection by server IDs, tags, or both.

Before You Start

• You have at least one VPS server in your account.
• You can open Cloud Panel and access Firewalls.
• You know which ports/protocols your app needs (for example SSH 22, HTTP 80, HTTPS 443).

Open the Firewall Console

1. In Cloud Panel, go to Firewalls.
2. Open /cloudpanel/firewalls.
3. Click Create Firewall to start.

Create a Firewall

Step 1 - Create the firewall object

Click Create Firewall, enter a name, and submit.

Step 2 - Understand default behavior

New firewalls are created with standard default outbound access so common egress traffic works immediately.

Step 3 - Open details

Click the firewall name to open /cloudpanel/firewalls/{id}.

From this page you can:

• Add and remove inbound rules
• Add and remove outbound rules
• Attach and detach servers
• Attach and detach tags
• Rename or destroy the firewall

Configure Inbound and Outbound Rules

In the firewall detail page, open the Rules tab.

Step 1 - Choose direction

• Click Add in Inbound rules to control traffic entering servers.
• Click Add in Outbound rules to control traffic leaving servers.

Step 2 - Select rule type

Use a preset (for example SSH, HTTP, HTTPS, MySQL, DNS, ICMP, All TCP, All UDP) or choose Custom.

Step 3 - Set protocol and ports

• Protocols: TCP, UDP, ICMP
• Ports: single port (443) or range (8000-8100)
• ICMP does not require a port value

Step 4 - Define sources or destinations

Depending on rule direction, define:

• All IPv4 and/or All IPv6
• Specific IPs or CIDRs (comma-separated)
• Tag names (comma-separated)

Step 5 - Save and verify

Save the rule, then confirm it appears in the rules table.

Use search in the Rules tab to quickly filter by protocol, ports, type, or source/destination.

Edit or Remove Rules

Step 1 - Edit existing rule

Use the pencil action on a rule row. The modal is pre-filled with current values.

Step 2 - Apply changes

Save the updated rule. The platform replaces the previous rule with your new configuration.

Step 3 - Remove rule

Use the remove action in the same row to delete a rule you no longer need.

Assign Servers to a Firewall

Open the firewall detail page and switch to the Servers tab.

Step 1 - Add servers directly

1. Click Add Droplets (servers).
2. Select one or more of your servers.
3. Confirm to attach them.

Step 2 - Remove a server

In the direct server list, click Remove next to the server.

Use Tags for Group-Level Protection

You can attach one or more tags to a firewall. Any server carrying that tag is protected by that firewall.

Step 1 - Add a tag to firewall

1. In Tagged Servers, click Add Tag.
2. Choose a tag from your tag list.

Step 2 - Confirm effective coverage

The Tagged Servers section displays matching servers per tag.

Step 3 - Remove a tag from firewall

Click Remove Tag in the tag header to detach it from the firewall.

Rename a Firewall

1. Open the firewall detail page.
2. Use Actions -> Rename.
3. Save the new name.

Destroy a Firewall Safely

Step 1 - Review dependencies

Before deletion, verify whether the firewall is still attached to critical servers or shared tags.

Step 2 - Destroy

Use Actions -> Destroy and confirm.

Step 3 - Validate

Return to /cloudpanel/firewalls and confirm it no longer appears.

Recommended Rule Baseline

A practical baseline for most web stacks:

• Inbound: allow SSH only from trusted IPs
• Inbound: allow HTTP/HTTPS from required public ranges
• Outbound: allow only required protocols and destinations
• Prefer tag-based targeting for production and staging groups

Troubleshooting

Rule saved but access still blocked

• Verify the rule is in the correct direction (inbound vs outbound).
• Check protocol and port accuracy.
• Confirm source/destination values are correct CIDRs or tags.

Server not appearing under tagged servers

• Ensure the server actually has the tag.
• Refresh the page after applying tag changes.

Firewall has zero servers in list

• You may only have tag-based assignments. Check Tagged Servers in addition to direct server assignments.

Frequently Asked Questions

Can one firewall protect multiple servers?

Yes. You can attach many servers directly and/or apply tags to protect groups.

Can I use both direct server assignment and tag assignment?

Yes. A firewall can include both target types.

Do I need to install an agent on servers?

No. Cloud Firewall is managed at the network layer by the platform.

What happens if I destroy a firewall?

The firewall object is removed and no longer enforces its rule set on previously attached targets.