Creating and Managing VPCs

This guide explains how to create a Virtual Private Cloud (VPC) in CloudRaya using the Control Panel.

Creating a VPC allows you to define custom IP ranges, subnets, and network access rules for your Virtual Machines.

Before You Begin

Before creating a VPC, make sure that:

• You have access to the CloudRaya Control Panel
• You are working inside the correct Project
• You understand that a VPC is scoped to a single Cloud Zone

If you are new to VPC concepts, see:

📄 Virtual Private Cloud (VPC)

Accessing the VPC Page

To manage VPCs:

1. Open the CloudRaya Control Panel
2. Navigate to Dashboard → Network → VPC

This page displays all VPCs created within your project.

You can filter VPCs by Cloud Zone.

Creating a New VPC

To create a new VPC, click Add VPC and follow the guided steps.

Step 1: Select Server Location

Choose the Cloud Zone where this VPC will be created.

• A VPC only exists within the Cloud Zone it was created in
• All subnets and VMs attached to this VPC will also be in that Cloud Zone

Step 2: Configure the VPC Network

Choose how the VPC's IP range is assigned:

• Generate by system (default)
  CloudRaya automatically generates the VPC, subnet, and ACL rules for you. No further input is required for this step.
• Add IP manually
  Configure the network yourself:
  • Set a VPC Name
  • Select the Network Size (for example, /19, /20, /24)
  • Select an available IP Address range from the list

CloudRaya prevents overlapping IP ranges within the same Cloud Zone.

Step 3: Create a Subnet

Next, define the first subnet inside the VPC.

For the subnet, configure:

• Subnet Name
• Network Size (CIDR), for example /24, /25
• IP Address range within the VPC network

Subnets determine where Virtual Machines are placed. Multiple VMs can be deployed within the same subnet.

You can add more subnets later. See Adding a Subnet to an Existing VPC below.

Step 4: Configure Access Control List (ACL)

In the final step, configure the ACL that will be applied to this subnet.

• Set the ACL Name
• Review the default allow rules (SSH 22, RDP 3389, HTTP 80, HTTPS 443)
• Add, edit, or remove ingress/egress rules as needed

After reviewing the configuration, click Add VPC to create the network.

📄 See: Access Control List (ACL)

Adding a Subnet to an Existing VPC

You don't need to create a new VPC to add more subnets. From an existing VPC, you can add additional subnets at any time.

Steps

1. Go to Dashboard → Network → VPC
2. Click View Detail on the VPC you want to add a subnet to
3. On the Subnet tab, click Add Subnet
4. Confirm the Server Location and VPC (both are fixed to the VPC you selected)
5. Configure the new Subnet (name, network size, IP address range)
6. Under ACL Rules, choose one of:
   • Select ACL - reuse an existing ACL profile already used by another subnet in this VPC
   • New ACL - create a new ACL profile with its own rules
7. Click Add Subnet

Reusing an existing ACL profile keeps access rules consistent across subnets that serve the same application, without recreating the same rules manually.

📄 See: Access Control List (ACL)

Viewing VPC Details

Once created, the VPC appears in the VPC list.

To view detailed information, click View Detail.

The VPC Detail page has three tabs:

• Subnet - lists all subnets in the VPC, including the ACL profile currently applied to each
• Access List - lists all ACL profiles created for this VPC, and which subnet(s) currently use each one
• Public IP - lists Public IPs associated with this VPC

Using a VPC When Creating a Virtual Machine

When creating a Virtual Machine, VPC Settings behave differently depending on whether you already have a custom VPC:

• No custom VPC exists
  CloudRaya automatically uses the default VPC. You can optionally click Create a VPC manually to set one up before deploying.
• One or more custom VPCs exist
  Click Select VPC to choose an existing VPC and Subnet from a dropdown. Before confirming, you'll see a read-only preview of:
  • How many VMs are already in that subnet
  • The ACL Rules that will apply to the VM (Ingress/Egress, by protocol)

This allows networking to be reviewed and confirmed before the VM is deployed.

When Should You Create a Custom VPC?

Creating a custom VPC is recommended when you need to:

• Separate environments such as production and staging
• Control private IP address allocation
• Apply custom network access rules
• Prepare for VPN connectivity
• Design a structured network layout

For simple workloads, the default VPC is sufficient.

Next Steps

After creating a VPC, you can continue with:

• Fine-tune network access rules.

  📄 Access Control List (ACL)

• Deploy VMs inside your VPC and subnets.

  📄 Create a Virtual Machine

• Expose selected services to the internet.

  📄 Public IP Address

• Connect external networks securely to your VPC.

  📄 VPN