Documentation

VPS Instances Overview

Virtual Private Servers (VPS) on DanubeData provide flexible, scalable compute resources for your applications.

What are VPS Instances?

VPS instances (also called "Pods" in the DanubeData interface) are virtual machines that give you:

  • Full root access via SSH
  • Choice of Linux distributions
  • Customizable resource profiles
  • Persistent storage
  • Public and private networking

Key Features

🖥️ Multiple OS Options

  • Ubuntu 20.04, 22.04, 24.04
  • Debian 10, 11, 12
  • CentOS 7, 8
  • Fedora 38, 39

⚡ High Performance

  • NVMe storage for fast I/O
  • Dedicated vCPUs
  • ECC RAM
  • 10 Gbps network

📊 Monitoring & Metrics

  • Real-time CPU usage
  • Memory utilization
  • Disk I/O
  • Network traffic

🔒 Security

  • Firewall integration
  • SSH key authentication
  • Private networking
  • Automatic security updates

Use Cases

  • Web Hosting: Host websites and web applications
  • Application Servers: Run backend services and APIs
  • Development: Create isolated development environments
  • CI/CD: Build and deployment servers
  • Microservices: Deploy containerized applications

Getting Started

1. Create a VPS Instance

  1. Navigate to Pods in the main menu
  2. Click Create Pod
  3. Configure your instance:
    • Choose an operating system
    • Select a resource profile
    • Add your SSH key
    • Configure networking
  4. Click Create Pod

Your VPS will be ready in 3-5 minutes.

2. Connect via SSH

Once your VPS is running:

ssh root@your-vps-ip

3. Install Software

Use your OS package manager to install software:

# Ubuntu/Debian
apt update && apt install nginx

# CentOS/Fedora
yum install nginx

Resource Profiles

Choose a profile based on your needs:

Profile vCPU RAM Storage Price/hour
Micro 1 1 GB 25 GB $0.007
Small 2 2 GB 50 GB $0.015
Medium 4 4 GB 80 GB $0.030
Large 8 8 GB 160 GB $0.060
XL 16 16 GB 320 GB $0.120

Networking

Public IP

Each VPS gets a public IPv4 address for external access.

Private Networking

Connect your VPS to other instances via private networks:

  • No internet exposure
  • Free internal traffic
  • Low latency

Firewalls

Attach firewalls to control traffic:

  • Inbound rules
  • Outbound rules
  • IP whitelisting

Storage

Root Volume

  • NVMe storage for OS and applications
  • Size based on resource profile
  • Included in instance pricing

Additional Volumes (Coming Soon)

  • Attach additional storage volumes
  • Expand storage independently
  • Snapshot and restore

Snapshots

Create point-in-time snapshots:

  1. Go to your VPS instance page
  2. Click Snapshots tab
  3. Click Create Snapshot
  4. Enter a name and description
  5. Click Create

Snapshots can be used to:

  • Backup before major changes
  • Clone instances
  • Migrate to different regions

Operations

Start/Stop

Control your instance state:

  • Stop: Shut down the instance (still billed for storage)
  • Start: Boot the instance

Reboot

Restart your instance from the dashboard.

Console Access

Access your VPS through the web console if SSH is unavailable.

Resize (Coming Soon)

Upgrade or downgrade your resource profile.

Monitoring

Track your VPS performance:

CPU Usage

Monitor CPU utilization and identify bottlenecks.

Memory Usage

Track RAM usage and swap activity.

Disk I/O

Measure read/write operations and IOPS.

Network Traffic

Monitor bandwidth usage (inbound/outbound).

Best Practices

Security

  1. Use SSH keys (disable password auth)
  2. Keep software updated
  3. Configure firewall rules
  4. Use fail2ban for brute-force protection
  5. Enable automatic security updates

Performance

  1. Monitor resource usage regularly
  2. Optimize applications for your profile
  3. Use caching where possible
  4. Implement CDN for static content

Reliability

  1. Take regular snapshots
  2. Use automation for deployments
  3. Monitor with external services
  4. Implement health checks

Cost Optimization

  1. Stop unused instances
  2. Right-size your resources
  3. Use spot instances for non-critical workloads (coming soon)

Troubleshooting

Can't Connect via SSH

  1. Check firewall rules
  2. Verify SSH key is correct
  3. Use web console for access
  4. Check SSH service status

High CPU Usage

  1. Identify process with top or htop
  2. Check for runaway processes
  3. Consider upgrading to larger profile

Out of Disk Space

  1. Check usage with df -h
  2. Clean up logs: /var/log/
  3. Remove old packages
  4. Consider adding storage volume

Next Steps

Need help? Contact our support team through the dashboard.