Firewall

Allow only authorized access to your servers

Cloud Firewall is a set of straightforward rules controlling which connections reach your server. Define it once and apply it to your servers.

Get startedPricing calculator
  • Pay by the hour for the time you use
  • Estimate costs before provisioning
  • Tehran data centers
ExampleFirewall rules
Example firewall rules: direction, protocol, port and allowed source
DirectionProtocolPortSourceStatus
InboundTCP22203.0.113.25/32Allow
InboundTCP800.0.0.0/0Allow
InboundTCP4430.0.0.0/0Allow
OutboundANYany0.0.0.0/0Allow

Try a connection

203.0.113.25 to port 22
A rule permits this connection; it reaches the server.

Estimate costs before provisioning.Pricing calculator

Quick start

Recommended starting rules

These two rules cover most web applications. Enable both when creating the firewall.

  • Administrative access only from your IP

    Open SSH only to your own IP or office IP. Other visitors cannot even attempt a password.

    TCP | 22 | your-ip/32
  • Public website access

    For a public website or application, allow web ports for everyone.

    TCP | 80, 443 | 0.0.0.0/0

These values are examples. Replaceyour-ipwith your real IP.

Define a rule

How to write a rule

Each rule has a few straightforward parts.

  1. Choose the direction

    Inbound rules control connections reaching your server; outbound rules control where your server connects.

  2. Protocol and port

    Select TCP, UDP or all protocols. ICMP and GRE are available only on supported infrastructure. For TCP and UDP, specify a port or port range.

  3. Specify the source

    Enter an IPv4 or IPv6 address or range. For a single IPv4 address, include the /32 suffix.

  4. Apply the firewall to a server

    Create the firewall once and apply it to your chosen servers. Review its status on the service page.

Before applying a rule

Common mistakes and how to avoid them

  • Leaving SSH open to everyone

    Allow administrative access only from your own IP.

  • Entering an IP without /32

    Include the suffix for a single IPv4 address, for example 203.0.113.25/32.

  • Opening database ports to everyone

    Allow database ports only from your private network range.

  • Creating a firewall without applying it

    After creating a firewall, apply it to the server and check its status on the service page.

  • Your own IP changes

    If your IP changes and access is blocked, update the rule with your new IP from the panel.

  • Looking for a deny rule

    All rules are allow rules. Connections you have not allowed cannot reach the server, so a separate deny rule is unnecessary.

Features

What is included

The main capabilities of Firewall at a glance.

  • Access rules

    Choose each rule's connection type, port and allowed source.

  • Apply to a server

    After confirmation, apply the firewall to your chosen server.

  • View status

    View the active firewall and its rules on the service page.

Use cases

Who it is for

  • Restrict administrative access
  • Make a website publicly accessible
  • Service access rules
User guide forFirewall
Recommended

Services commonly used alongside Firewall.

Frequently asked questions

Before you start

What problem does Firewall solve?

Without clear inbound rules, servers are exposed to unwanted access. Fragmented settings make control harder.

What is Firewall suitable for?

Firewall supports use cases such as Restrict administrative access, Make a website publicly accessible, Service access rules. The right choice depends on your project's technical and operational requirements.

How do I get started with Firewall?

Read the product guide and estimate costs in the calculator, then create the service in your chosen project in the client panel.

Get started with Firewall

Register, estimate costs before provisioning and pay hourly for the time you use the service.