"Firewall Rules"
Core Rule Elements
Direction
Protocol
IP Version
Traffic Flow ControlIngress (Incoming) Controls traffic coming into your VM Typical for services your VM provides Examples: Web servers, databases, SSH access Source IP restrictions apply to incoming connections Egress (Outgoing) Controls traffic leaving your VM Typical for services your VM consumes Examples: API calls, database connections, internet access Destination IP restrictions apply to outgoing connections
Adding Firewall Rules
Access Rule Management
From the firewall details page or click "Add Rule" button on firewall card
Configure Direction
Select traffic direction:Ingress: For incoming traffic (most common) Egress: For outgoing traffic
Select Protocol
Choose the appropriate protocol:TCP: For web services, SSH, databases UDP: For DNS, streaming, real-time applications ICMP: For ping and network diagnostics
Set IP Version
Choose IP version:IPv4: Standard choice for most applications IPv6: For modern applications requiring IPv6
Configure IP Range
Enter remote IP range in CIDR format:Specific IP: 203.0.113.1/32 IP Range: 192.168.1.0/24 All IPs: 0.0.0.0/0 (IPv4) or ::/0 (IPv6)
Set Port Range (TCP/UDP only)
For TCP and UDP protocols, specify port ranges:Single Port: Set both min and max to same value Port Range: Set minimum and maximum ports Port Numbers: Must be between 1 and 65535
Save Rule
Click "Add Rule" to save the configuration
Port Range Specifications
Port Configuration Requirements
Common Port Configurations
Single Ports
Port Ranges
Well-Known Ports
Specific Service Ports
| Service | Protocol | Port | Min/Max Setting |
|---|---|---|---|
| SSH | TCP | 22 | Min: 22, Max: 22 |
| HTTP | TCP | 80 | Min: 80, Max: 80 |
| HTTPS | TCP | 443 | Min: 443, Max: 443 |
| MySQL | TCP | 3306 | Min: 3306, Max: 3306 |
| PostgreSQL | TCP | 5432 | Min: 5432, Max: 5432 |
| Redis | TCP | 6379 | Min: 6379, Max: 6379 |
IP Range Validation
IPv4 CIDR Examples
IPv6 CIDR Examples
CIDR Validation Rules
Common Rule Configurations
Web Server Rules
Basic Web Server
API Server
HTTP/HTTPS Traffic
| Purpose | Direction | Protocol | Port | Remote IP | Use Case |
|---|---|---|---|---|---|
| Public HTTP | Ingress | TCP | 80 | 0.0.0.0/0 | Public website |
| Public HTTPS | Ingress | TCP | 443 | 0.0.0.0/0 | Secure website |
| SSH Access | Ingress | TCP | 22 | Your IP/32 | Server management |
| Health Check | Ingress | TCP | 80 | Load balancer IP | Monitoring |
Database Server Rules
Application-Specific Rules
Jupyter Notebook
Docker Registry
Monitoring Services
Data Science Environment
Purpose: Jupyter Web Interface
Direction: Ingress
Protocol: TCP
Port: 8888
Remote IP: Your IP address or trusted network
Security: Use strong password and HTTPSNetwork Diagnostic Rules
Security Best Practices
Rule Design Principles
Start Restrictive
Begin with the most restrictive rules and gradually open access as needed
Document Purpose
Add clear descriptions to rules explaining their purpose and requirements
Use Specific IPs
Avoid 0.0.0.0/0 unless public access is truly required
Regular Review
Periodically audit rules and remove unnecessary access