RamNode logo
    Sign UpLogin
    Back to Cloud VPS Documentation

    Resize Instance

    Scale your resources up or down to match your needs

    Overview

    Cloud instances can be resized to different flavors (plans) to increase or decrease resources like CPU, RAM, and disk space. This flexibility allows you to scale your infrastructure as your needs change.

    Before You Resize

    Important Considerations

    • Backup Your Data: Always create a snapshot or backup before resizing
    • Plan Downtime: Resizing requires a reboot and brief downtime
    • Disk Considerations: You can only resize to flavors with equal or larger disk space
    • Availability: The target flavor must be available in your region

    Resize Process

    Step 1: Select Instance

    1. Log into the Cloud Control Panel
    2. Select your instance from the Instances tab

    Step 2: Choose New Flavor

    1. Click the Resize Instance button in the instance actions dropdown
    2. Select the new flavor (plan) from the available options
    3. Click Resize to begin the process
    Resize Instance

    Step 3: Wait for Completion

    The instance will shut down, resize, and boot up with the new configuration. This process typically takes a few minutes.

    Confirming the Resize

    After the resize completes, you'll need to confirm or revert the change:

    Confirm Resize

    Accept the new configuration and complete the resize

    Revert Resize

    Roll back to the original flavor if something went wrong

    During this confirmation period, test your instance to ensure everything works correctly with the new resources.

    After Resizing

    Expanding Disk Space

    If you resized to a flavor with more disk space, you may need to expand your filesystem:

    For ext4 filesystems (most Linux distributions):

    # Check current disk usage
df -h

# Resize the partition (if needed)
growpart /dev/vda 1

# Resize the filesystem
resize2fs /dev/vda1

# Verify new size
df -h

    For XFS filesystems:

    # Resize the partition (if needed)
growpart /dev/vda 1

# Resize the filesystem
xfs_growfs /

# Verify new size
df -h

    Downgrading Considerations

    When downgrading to a smaller flavor:

    • Disk Space: Cannot downgrade to a flavor with less disk space than currently allocated
    • Memory Usage: Ensure your applications can run within the reduced RAM
    • CPU Performance: Be prepared for reduced processing power
    • Testing: Monitor your instance carefully after downgrading

    Resize Limitations

    • Cannot resize to flavors with smaller disk allocations
    • Some flavors may not be available in all regions
    • Instances must be stopped or will be stopped automatically during resize
    • IP addresses and other network configurations are preserved

    Flexible Scaling

    With hourly billing, you only pay for the resources you use. Feel free to experiment with different instance sizes to find the perfect fit for your workload, and resize as your needs change.