Qumulus
  • Welcome
  • Getting Started
    • Introduction to QUM
      • What can 1 QUM do?
      • QUM Performance
    • Dashboard
  • Your Account
    • Your Projects
      • Project Architecture
  • Resources
    • Compute
      • Instances
        • Creating an Instance
        • Instance Configuration
          • OS & Images
          • Instance Types
        • Using User Data
        • Connecting to an Instance
        • Instance Details
        • Instance Actions
        • Instance Monitoring
      • Instance Snapshot
        • Create & Restore
        • Snapshots Manage
  • Storage
    • Volumes
      • Create & Attach
      • Resize & Delete
    • Volume Snapshots
  • Networking
    • Public IPs
      • IP Allocation/Management
      • Associating/Disassociating IPs
    • Load Balancer
  • Security
    • Key Pairs
      • Creating Key Pairs
      • Managing Key Pairs
    • Security Groups
      • Managing Security Groups
    • SSL Certificates
  • How-To & Tutorials
    • Fixed cost Development Playground
    • Installing Redis Community
    • Installing Mongo Community
    • Installing PostgreSQL
    • VPN Server
      • VPN Server with OpenVPN
      • VPN Server with Netbird
  • RELEASES
    • Q1, 2025
  • Blogs
    • Release Beta v1.0
  • Release v2.0
Powered by GitBook
On this page
  • Overview
  • Key Concepts
  • Creating Security Group
  • Security Group Rule
  • Deleting Security Group
  1. Security

Security Groups

PreviousManaging Key PairsNextManaging Security Groups

Last updated 1 month ago

Overview

In Qumulus, Security Groups act as virtual firewalls for instances (virtual machines), controlling both inbound and outbound traffic at the network interface level. They are a key part of Qumulus network security model.

Security Groups provide a way to define a set of IP filter rules that determine what type of traffic is allowed to or from an instance. These rules are stateful, meaning that if you allow an incoming connection, the corresponding outgoing response is automatically allowed.

Key Concepts

Term
Description

Security Group

A container for firewall rules. It can be associated with one or more instances

Rule

A single access control entry that defines traffic type such as protocol, port, source allowed in or out of instances.

Default Group

All projects come with a default security group which denies all ingress and allows all egress unless modified

Creating Security Group

In Security Groups section, click create Security Group and give it a friendly name. It may be a good idea to give some description which can give some insights on what this security group does and for what purpose it was created.

You can create up to 50 Security Groups in your project. This limit is sufficient for most use cases, in case you need more for your use case, you can get it increased by raising a support ticket to us.

Security Group Rule

Select the Security Group in which you want to create the rule. You can create Inbound rule from within Inbound Rules tab and an outbound rule from Outbound Rules tab.

1

Select Type

You can select the type of Rule from the list, you would find various pre-defined rule types you can select from or you can select Custom TCP/Custom UDP if you can not find required Rule Type

2

Port Range

You can specify Port/Port Range for Custom TCP/UDP Rule Type. You may define an integer or a port range i.e. 80 or 1-65535. Maximum allowed port is 65535.

3

Remote Type

Custom IP: If you want to add a custom IP Range

Security Group: If you want to define network traffic to/from an existing Security Group

MY IP: If you want to use your current Public IP Address

Anywhere: If you want to allow traffic for the entire internet. Be careful while selecting Anywhere for Inbound Rule

4

Remote IP

If you have selected Custom IP, you can provide a valid IPv4 range.

5

Description

You may want to add some description for later reference against that rule.

Deleting Security Group

Click three-dot (⋮) under the Action column and click delete.