Knowledge Base · Compute
Creating a Virtual Machine on CloudPe
A complete step-by-step guide to deploying a fully configured Virtual Machine on the CloudPe Cloud Management Platform — from first login to a running instance.
⏱ 5–10 minutes👤 All Users📍 Mumbai (IN-WEST2 / IN-WEST3)📅 CloudPe 2026
💻
What You’ll Accomplish
This guide covers every field on the CloudPe VM creation form — VM name, instance count, region, project, compute flavor (vCPU & RAM), OS image, boot volume, network, security group, SSH key, and pricing summary — before clicking Create VM.
✓
Prerequisites
Ensure these are in place before you begin
🔑
Active Account
Verified account at app.cloudpe.com
💰
Wallet Balance
Sufficient balance for at least one billing cycle
📁
Project Created
At least one project exists in your account
🌐
Private Network
A network in your target region (recommended)
🛡
Security Group
Default or custom security group available
🔐
SSH Key (Optional)
Public key uploaded under Billing → SSH Keys
1
Login & Access the Dashboard
Sign in and verify the main dashboard
1
Navigate to the CloudPe Portal
Open your browser and go to app.cloudpe.com. Enter your registered email and password, then click Sign In.
2
Confirm the Dashboard Has Loaded
After login you land on the Dashboard. Verify the left navigation (Compute, Storage, Networking), Wallet Balance, Virtual Machines count, and Recent VMs panel are all visible.
Dashboard ShortcutsTwo quick-start links are available: the + Create VM button top-right, and Create your first VM in the Recent VMs panel. Both open the creation form directly.
Low Balance WarningCheck your Wallet Balance before proceeding. If negative, navigate to Billing & Account → Billing → Add Funds and top up first.
2
Navigate to Virtual Machines
Open the VM list and start the creation flow
1
Expand the Compute Menu
In the left sidebar click Compute. The submenu reveals: Virtual Machines, GPU VMs, Kubernetes, and VDI Sessions (Beta).
2
Click “Virtual Machines”
Select Virtual Machines from the submenu. The VM list page opens showing existing VMs, or an empty state if none exist yet.
3
Click “+ Create VM”
Click the purple + Create VM button (top-right) to open the configuration form at
/dashboard/vms/create.Shortcut AvailableThe + Create VM shortcut on the Dashboard goes straight to the creation form, bypassing the VM list entirely.
3
VM Name & Number of Instances
Give your VM a unique name and set how many to deploy
1
Enter a VM Name and Set Instance Count
The first field on the Create VM form is VM Name. Below it is the Number of Instances +/− spinner.
Naming ConventionUse a pattern such as
env-role-number e.g. prod-web-01 or dev-db-02 to keep VMs identifiable as your infrastructure grows.4
Select Region & Project
Choose the data centre location and project for this VM
1
Choose a Region
Click one of the region cards to select where your VM will be physically deployed.
Region StrategyLowest latency: pick the region nearest your users. High availability: deploy across Zone A and Zone B. Disaster recovery: span across DC2 and DC3.
2
Select a Project
Click a project card to assign this VM. Projects group resources and attribute costs for billing.
No Project Visible?Navigate to Billing & Account → Projects to create one first. Every VM must belong to exactly one project.
5
Choose VM Size (Compute Flavor)
Select the vCPU and RAM configuration for your workload
1
Select a Flavor Category
The Size section provides three category tabs. Click a tab to filter the size tiles displayed below it.
CPU Optimized
1:2 CPU-to-RAM
Build servers, batch processing, game servers, high-frequency APIs.
From ₹0.75/hr (2 vCPU / 4 GB)
General Purpose
1:4 CPU-to-RAM
Web apps, REST APIs, dev environments, small-to-medium databases.
Balanced pricing
Memory Optimized
1:8 CPU-to-RAM
Redis, large databases, real-time analytics, ERP systems.
Higher RAM-to-CPU ratio
2
Select a Specific Size Tile
Click the tile matching your requirements. Available CPU Optimized sizes:
Right-Sizing AdviceStart with the smallest size that meets your requirements. CloudPe allows resizing after creation (VM briefly powers off). Over-provisioning increases cost without performance benefit.
6
Select Operating System
Choose a CloudPe-managed OS image or a custom image
1
Select Image Type and Distribution
Two tabs: OS Images (CloudPe-managed) and Custom Images (user-uploaded). Click a distribution to expand its versions, then select the specific version.
Recommended DefaultUbuntu 24.04 LTS is pre-selected and recommended for most new deployments — longest LTS cycle, broadest package availability, and the largest community knowledge base.
7
Select Billing Period
Choose your payment cycle — longer commitments unlock significant discounts
1
Choose a Billing Cycle
Below the OS selection, the Billing Period row shows five card options. Click the card that matches your project timeline.
⚠ Billing Period is Locked After LaunchThe billing cycle cannot be changed after the VM is created. Hourly VMs can be stopped to pause billing. Reserved plans (Monthly and above) are billed for the full committed period regardless of usage.
8
Storage Configuration
Set boot volume size and attach additional persistent volumes
1
Select a Storage Policy (NVMe Tier)
CloudPe uses all-NVMe storage. Choose a performance tier for your boot volume. The tier determines IOPS, throughput, per-GB pricing, and the replication/resilience model.
Eco NVMe
IOPS up to 15,000
Throughput up to 500 MB/s
₹4.50 / GB / mo
Dev/Test · Staging · Low-traffic sites
• Erasure Coding (not replication) — slower recovery on disk/server failure
• Cannot migrate to Standard / Pro NVMe — requires data migration to a new volume
Standard NVMe
IOPS up to 25,000
Throughput up to 1,000 MB/s
₹6.20 / GB / mo
Most production workloads · Web apps · APIs
• 3× Replication — fast recovery on disk/server failure
• Can upgrade to Pro NVMe without downtime
• Renamed from General Purpose
Pro NVMe
IOPS up to 50,000
Throughput up to 2,000 MB/s
₹8.00 / GB / mo
Databases · ERP (SAP) · GPU VMs · High-I/O analytics
• 3× Replication — fast recovery on disk/server failure
• Can downgrade to Standard NVMe without downtime
⚠ Eco NVMe — Important LimitationEco NVMe uses Erasure Coding instead of 3× Replication, which means slower recovery after a disk or server failure. Crucially, you cannot migrate an Eco NVMe volume to Standard or Pro NVMe in-place — you must create a new volume on the target tier and copy your data across. Only choose Eco if cost is the primary concern and the workload tolerates longer recovery windows.
✅ Standard NVMe → Pro NVMe: Live UpgradeIf you start on Standard NVMe and later need higher performance, you can upgrade to Pro NVMe without any downtime or data migration. Pro NVMe can similarly be downgraded back to Standard NVMe live.
2
Configure Boot Volume Size
Set the root disk size. The minimum is determined by the selected OS image. Increase it to accommodate application data.
Storage PlanningFor web servers 30–50 GB is typically sufficient. For databases or media workloads, provision 100 GB or more. Additional volumes can be attached at any time via Storage → Volumes.
3
Attach Additional Volumes (Optional)
Click + Add Volume to attach persistent block storage beyond the boot disk. Specify size, volume type, and whether to retain or delete the volume on VM termination.
Volume PersistenceAdditional volumes can be detached and reattached to different VMs. Always select Keep on termination for data volumes to prevent accidental loss.
9
Network Setup
Configure public and private network interfaces
1
Configure Network Interfaces
Enable or disable public and private network interfaces as required for your workload.
Security ReminderEnabling Public Network exposes your VM to the internet. Always configure Security Group rules (Step 9) to restrict inbound traffic to only the required ports and source IP ranges.
10
Security & Authentication
Assign security groups and configure access credentials
1
Assign Security Group, SSH Key & Root Password
The Security section contains three configuration items.
SSH Keys Are Strongly PreferredSSH key authentication is significantly more secure than passwords and immune to brute-force attacks. Use an SSH key for all production VMs.
Save Auto-Generated Passwords ImmediatelyIf you click Generate, store the password in a password manager right away. CloudPe will not display it again after VM creation.
11
Advanced Options
Cloud-init scripts, metadata tags, and availability zone settings
1
Configure Advanced Options (Optional)
Expand the Advanced Options accordion to access additional settings. Skip for standard deployments — configure the server manually via SSH after creation.
Automating First-Boot SetupUse User Data to install Nginx, configure firewall rules, or pull your app code — all completed automatically before your first SSH login.
12
Review & Launch the VM
Verify the full configuration summary and deploy the instance
1
Review the Pricing Summary Panel
The summary panel at the bottom updates in real-time as you adjust selections. Verify each line item carefully before proceeding.
Example Configuration & Pricing Summary
VM Namemy-web-server
RegionMumbai DC3 (IN-WEST3)
Operating SystemUbuntu 24.04 LTS
Size2 vCPU · 4 GB RAM (a.cpu1.4g)
Storage30 GB Boot Volume
NetworkPublic IP + Private Network
Total (Monthly)₹881.64
Approximately ₹1.22 per hour
2
Click “Create VM”
Click the Create VM button at the bottom of the form. CloudPe immediately begins provisioning and redirects you to the VM detail page.
Provisioning TimeVM provisioning typically completes within 60–120 seconds. Status transitions from Building to Active. The public IP is displayed once Active.
Button Appears Disabled?The Create VM button remains inactive until a valid VM Name has been entered. Scroll to the top, complete the VM Name field, and the button will become clickable.
?
Frequently Asked Questions
Common questions about VM creation on CloudPe
Can I resize my VM after it is created?
Yes. Navigate to Compute → Virtual Machines, click your VM, and use the resize option from the detail page. The VM briefly powers off during resize. All volumes are preserved.
How do I connect to my VM after creation?
Once the VM shows Active, connect via SSH:
ssh root@. Add -i /path/to/key for key-based auth. The public IP is on the VM detail page. For Windows VMs, use RDP on port 3389.The “Create VM” button is disabled — why?
The button remains inactive until a valid VM Name is entered. Scroll to the top of the form, complete the VM Name field (letters, numbers, hyphens, underscores only), and the button will activate.
Can I deploy multiple identical VMs simultaneously?
Yes. Use the Number of Instances spinner in Step 3. CloudPe provisions all VMs at once with numeric suffixes (e.g.
my-web-01, my-web-02).How do I add more storage to an existing VM?
Go to Storage → Volumes, click Create Volume, then attach via Actions → Attach Volume on the VM detail page. Use
fdisk, mkfs, mount inside Linux to partition and mount.What happens if my wallet balance runs out?
Your VM will be suspended when the balance reaches zero. CloudPe sends email notifications before this threshold. Top up via Billing & Account → Billing → Add Funds. Suspended VMs are deleted after a grace period if not renewed.