Constellation Network
IntroductionFundamentalsFor DevelopersNode Validators
  • Index
  • Introduction
  • Elements
    • Toolkit
    • Development Environment
    • Hydra CLI
    • Developer Dashboard
    • Telemetry Dashboard
    • Metagraph Monitoring Service
  • Metagraph Framework
    • Overview
    • Framework Architecture
    • Installation
    • Currency
      • Working with Tokens
    • Data
      • State Management
      • Lifecycle functions
    • Framework Endpoints
    • Custom Endpoints
  • Guides
    • Quick Start
    • Send a Transaction
    • Manual Setup
    • Customize Rewards Logic
    • Custom Data Validation
    • Working with p12 files
    • Snapshot Fees
    • Deploy a Metagraph
      • Security groups
      • Key pairs
      • Base instance
        • Generating base instance
        • Connect to the instance
        • Generating AMI (Image) from Base Instance
        • Launching instances from AMI
      • Start Metagraph Instances
        • Configuring P12 Files
        • Start Global L0 Instances
        • Start Metagraph L0 Instances
        • Start Currency L1 Instances
        • Start Data L1 Instances
  • Resources
    • Network APIs
    • Example Codebases
    • Metagraph Development Video Series
Powered by GitBook

Main

  • Website
  • Get DAG
  • Explore Projects
  • Partners

Socials

  • Telegram
  • Discord
  • X (Twitter)

Tools

  • Wallet
  • DAG Explorer
  • Coingecko

© 2025 CONSTELLATION NETWORK

On this page

Was this helpful?

Export as PDF
  1. Guides
  2. Deploy a Metagraph

Security groups

PreviousDeploy a MetagraphNextKey pairs

Last updated 1 month ago

Was this helpful?

Security groups act as virtual firewalls that control inbound and outbound traffic to your instances. Our 3 nodes will need to open up connection ports for SSH access, and for each of the 4 network layers to communicate over.

Create a Security Group

First, navigate to the Security Groups section in the Amazon .

Menu ec2

Create a new security group and provide a name, for example MetagraphSecurityGroup.

Inbound rules define which ports accept inbound connections on your node. We will need to open up ports for SSH access and for each of the metagraph layers.

Click Add Rule under the Inbound Rules section and add the following rules:

Type
Protocol
Port Range
Source
Purpose

SSH

TCP

22

0.0.0.0/0

SSH access

Custom TCP

TCP

9000-9002

0.0.0.0/0

gL0 layer

Custom TCP

TCP

9100-9102

0.0.0.0/0

mL0 layer

Custom TCP

TCP

9200-9202

0.0.0.0/0

cL1 layer

Custom TCP

TCP

9300-9302

0.0.0.0/0

dL1 layer

Click on Create Security Group

Add Inbound Rules

​
​
​
EC2 console