Prerequisite: You need an existing VPC network before creating a security group.
Summary
This page explains how to create and manage security groups in the Nscale Console UI. Use this workflow if you:- Need to control which traffic can reach your instances and clusters
- Want to define reusable firewall rules within a VPC
- Are setting up networking before creating instances (a security group is required)
Availability
This feature is available for On-demand and Reserved cloud services.Requirements
- A VPC network to associate the security group with
- Permission and sufficient quota to create security groups
Default behaviour: With no rules defined, all inbound and outbound traffic is denied. You must add rules to allow the traffic your workloads need.
Key Concepts
- Inbound rules control traffic coming into your resources (e.g., SSH connections from your IP)
- Outbound rules control traffic going out from your resources (e.g., internet access for package downloads)
- Stateful: If you allow an inbound connection, the return traffic is automatically allowed (and vice versa)
CIDR Notation
Security group rules use CIDR notation to specify IP ranges:Protocol Reference
| Protocol | When to Use |
|---|---|
| TCP | Most common — used for SSH (port 22), HTTP (80), HTTPS (443), and application traffic |
| UDP | Used for DNS (port 53), some streaming/gaming protocols |
| Any | Allows all protocols — use with caution |
| VRRP | Virtual Router Redundancy Protocol — used for high-availability failover. Most users don’t need this; use TCP/UDP/Any instead |
Common Rule Examples
| Use Case | Direction | Protocol | Port Range | Source/Destination CIDR |
|---|---|---|---|---|
| Allow SSH access | Inbound | TCP | 22 | 0.0.0.0/0 or your IP (x.x.x.x/32) |
| Allow HTTP traffic | Inbound | TCP | 80 | 0.0.0.0/0 |
| Allow HTTPS traffic | Inbound | TCP | 443 | 0.0.0.0/0 |
| Allow all outbound | Outbound | Any | All | 0.0.0.0/0 |
Security Group Lifecycle
| Action | Details |
|---|---|
| Create | Provide a name, select a VPC, add an optional description, and define rules |
| Edit rules | Add, modify, or remove individual rules at any time |
| Delete | Remove the security group when it is no longer needed |
Step-by-step
Create a security group
- In the Console left navigation, go to Network → Security Groups
- Click the + New button in the top-right corner
-
A side panel opens with the creation form:
- Name: Enter a name for the security group
- VPC: Select the VPC this security group will belong to
- Description (optional): Add a description (up to 200 characters)
-
Click Add Rules to define your firewall rules:
- Choose Inbound or Outbound
- Select the Protocol (TCP, UDP, Any, or VRRP)
- Enter the Port Range (e.g.,
22for SSH,80for HTTP, or1-65535for all ports) - Enter the CIDR block (e.g.,
0.0.0.0/0for all IPs) - Add as many rules as needed
- Click Create to save the security group
Managing security groups
To edit an existing security group:- Go to Network → Security Groups and select the security group
- Add, modify, or remove rules as needed
- Save your changes
- Ensure no resources are attached to it
- Go to Network → Security Groups, select the security group, and delete it
Common Issues / Troubleshooting
- Symptom: Can’t delete a security group. Likely cause: The security group is attached to one or more active resources (instances, clusters). Fix: Remove or delete the associated resources, then try deleting the security group again.
-
Symptom: Instance is unreachable via SSH.
Likely cause: No inbound rule for SSH (TCP port 22) in the instance’s security group.
Fix: Go to Network → Security Groups, select the security group attached to the instance, and add an inbound rule for TCP port 22 from your IP or
0.0.0.0/0. -
Symptom: Instance can’t download packages or reach the internet.
Likely cause: No outbound rules defined. By default, all outbound traffic is denied.
Fix: Add an outbound rule allowing the required protocols and ports (or allow all outbound with protocol Any to
0.0.0.0/0).
Related Resources
VPC Networks
Create the VPC your security group belongs to
Instances
Attach security groups when creating instances
Terraform Provider
Manage security groups as infrastructure as code
API Reference
Manage security groups programmatically via the Networking and Storage API