Security
Cloud firewalls, applied by server or by label
An Odinex firewall is a set of stateful rules that filters traffic in the network before it reaches your servers. Inbound traffic is blocked unless a rule allows it, replies to allowed connections always pass, and a firewall can follow servers by label so new servers are protected automatically.
At a glance
- Type
- Stateful
- Protocols
- TCP, UDP, ICMP, ESP, GRE
- Rules
- Up to 50 per firewall
- Applied to
- Servers or label selectors
- Price
- No extra charge
Key features
Deny by default
Once a firewall applies, only the inbound traffic you allow reaches the server.
Stateful
Replies to allowed connections are always let through, so you write rules only for what starts a connection.
Apply by label
Apply a firewall to role=web and every matching server, now or later, gets the rules.
Protected from first boot
Pass up to five firewalls when creating a server, so it is never exposed.
Inbound and outbound
Limit outbound connections too, by destination address and port.
Outside the server
Rules are enforced in the network, so a mistake inside the OS cannot open a port.
What it is used for
SSH from the office only
Allow port 22 from your own address range and HTTP and HTTPS from everyone.
Lock down databases
Accept database connections only from your application servers.
Fleet-wide policy
One firewall per role, applied by label, so every new server is protected without extra steps.
Try it
odx firewall create --name web --rules-file rules.json
odx firewall apply-to-resource --type label_selector --label-selector role=web webDocumentation
Firewalls: questions and answers
Clear answers about location, infrastructure and billing.
Do firewalls cost extra?
Is a server protected without a firewall?
What happens if several firewalls apply?
Does it replace a firewall inside the OS?
Build it in Frankfurt today
Create an account, top up from €5 and pay by the hour, never more than the monthly price.