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
  1. Security
  2. Security Groups

Managing Security Groups

Security Groups in Qumulus enable virtual firewall capabilities to manage incoming and outgoing network traffic for your virtual instances. When security groups are correctly managed, organizations improve their network security and achieve better operational efficiency.

Accessing Security Groups

To manage your security groups:

  1. Sign in to your Qumulus Cloud account.

  2. Navigate to Security > Security Groups.

  3. Choose your desired group by clicking on its name.

Understanding Security Group Rules

Security Groups contain two different rule types, which include inbound rules and outbound rules.

  • Inbound Rules: Define the permitted incoming traffic.

  • Outbound Rules: Control the allowed outgoing traffic.

Each rule is detailed as follows:

Field
Description

Ether Type

Specifies the IP version (IPv4 or IPv6).

Type

Indicates the service or protocol (e.g., SSH, HTTP, HTTPS).

Protocol

Network protocol used (TCP, UDP, ICMP, etc.).

Port Range

Specifies the ports that the rule will either regulate specifically or through ranges.

Remote IP

Allowed IP addresses or CIDR blocks.

Description

Optional note or context for the rule.

Creating Inbound and Outbound Rules

Adding an Inbound Rule

To create a new inbound rule:

GUIDEFLOW

  1. Choose the desired Security Group.

  2. Navigate to the Inbound Rules tab.

  3. Click on Create Inbound Rule in the right corner.

  4. Set the following parameters:

  • Type: Select from a list of predefined protocols (SSH, HTTP, PostgreSQL, etc.) or choose a custom protocol.

  • Protocol & Port Range: Automatically set based on the selected Type, or it can also be manually configured.

  • Remote Type: Select from Custom IP, Security Group, My IP, or Anywhere.

  • Remote IP: Specify the IP or CIDR block (e.g., 192.168.1.0/24).

  • Description: (Optional) Provide additional Context or notes.

  1. Hit the ✅ button to execute the rules.

Adding an Outbound Rule

You can control outbound traffic flow by using the same procedure under the Outbound Rules tab.

Recommended Best Practices
  • Open only necessary ports for your applications.

  • Limit your inbound rules to specific IP addresses or CIDR blocks whenever possible.

  • Security group rules should be audited periodically and all unused entries should be removed.

PreviousSecurity GroupsNextSSL Certificates

Last updated 21 days ago