Skip to main content

How to Resize Instances

Open the Instance's upgrade page to see which package and resource changes are available for that service. The options, price and billing cycle shown for your account determine what you can request.

Considerations Before Resizing​

  • Keep a recoverable copy of the server's data outside the Instance before changing its resources. Review the snapshot workflow if your service supports it.
  • The inspected upgrade page warns that automatic upgrades or downgrades resize the disk and restart the VM, and that reducing resources may cause data loss. Read the warning for the selected change and arrange an appropriate maintenance window. The page does not establish a fixed downtime estimate.
  • Confirm the target disk size and how the guest's partitions and filesystem must be handled. Do not assume that every decrease or expansion is supported for your service.
  • Review resource prices, the selected billing cycle and any amount due before submitting. The presence of an IPv6 option does not by itself establish that it is free.

Resizing Instances with the API​

The published Upgrade Options operation lists options with GET /api/service/{id}/upgrade/, where id is the service ID. Use the API reference's authentication method. For example:

curl --request GET \
--url 'https://cloud.fibacloud.com/api/service/{id}/upgrade/' \
--header 'Authorization: Basic <credentials>'

Replace the placeholders with your authorized service ID and authentication value. The response defines available package and resources choices; use their returned identifiers and values.

Upgrade Request uses POST on the same route. Its documented parameters include package, cycle, resources and send. The operation distinguishes an estimate from a submitted request: send: true submits the upgrade request. Consult the operation's parameter definitions and review the estimate before intentionally submitting a change. Inspect the response and any payment requirements; an estimate is not confirmation of an applied resize.

These instructions follow the published API contract. No upgrade API request was executed for this guide.

Resizing Instances with the Control Panel​

  1. Open Instances, select the intended service and choose Upgrade from its management menu.
  2. Read the restart and data-loss warning. The page has separate sections for resource changes and a package change, each with its own Save Changes button.
  3. Review the options offered for your service. The inspected resource section included Additional Storage, IPv4, IPv6 and Cloud Backups; availability and prices must be checked on your own form.

Resizing Instances with package​

In the package section, review Upgrade / Downgrade to:, the proposed CPU/RAM/disk and the billing cycle. Before using that section's Save Changes, confirm the selected service, requested resources and charges, and prepare for the page's stated restart behavior. Follow any confirmation or payment steps presented by the panel.

After the request is processed, verify the service's status and assigned resources, then check the guest's disk, filesystem and applications. Keep your recovery copy until those checks are complete. The page was inspected without saving a change; this guide does not claim a measured resize duration or a successful resize test.