Resize a Cloud Server
Plan the resource change, understand service interruption and verify the application after the resize.
Choose the new resource level
Review current application usage before increasing resources. More RAM can help a memory-constrained workload, while CPU-heavy work needs additional processing capacity. Scaling infrastructure does not correct an application bottleneck by itself.
Plan for interruption
Some Cloud Server resource changes require a restart. Perform disruptive changes during an appropriate maintenance window and make sure important data is protected before starting.
Resize from the Control Center or AI Operator
Use the Cloud Server controls in the Control Center. AI Operator can also prepare supported resize operations; disruptive changes require confirmation when appropriate.
Verify after the change
Confirm that the server returns to a healthy state and test the application, database and external endpoints that depend on it.
Documentation covers the standard workflow. For a live account or platform issue, contact CloudBalkan support without sending passwords, private keys or other secrets.
Open support options →