Can servers be resized after deployment?
Yes, OCI servers can be resized after deployment, but the process and the impact (like downtime) depend on the type of server you are "renting."
In 2026, Oracle's Flexible Shapes have made this process much more granular compared to the old "t-shirt size" models of other clouds.
If you are using a Flexible Shape (like VM.Standard.E5.Flex), you have incredible control over resizing.
What you can change: You can independently adjust the number of OCPUs and the amount of RAM. For example, you can take a server from 2 cores/16GB to 4 cores/64GB without needing to touch the storage.
Downtime: Resizing a VM requires a reboot. When you save your changes, OCI automatically restarts the instance on a physical host that can accommodate the new resource requirements.
Compatibility: You can generally switch between different generations of the same processor family (e.g., AMD E4 to E5) as long as the underlying OS image supports the new hardware.
Bare Metal servers are physical hardware, so they cannot be "resized" in the traditional sense.
The Workflow: To change a Bare Metal server's size, you must terminate the current server (while preserving the boot volume) and launch a new Bare Metal server using that same boot volume.
Downtime: This is a manual process that involves significant downtime (usually 5–10 minutes for the new hardware to provision).
While resizing (Vertical Scaling) is great for handling a permanent increase in load, OCI also supports Autoscaling (Horizontal Scaling):
Instance Pools: You can set a rule that says, "If CPU usage stays above 70% for 10 minutes, add two more servers."
The Benefit: This handles traffic spikes without requiring a reboot of your primary server.
| Server Type | Can Resize? | Downtime? | Complexity |
| Flexible VM | Yes | Yes (Reboot) | Low (Slider in Console) |
| Standard VM | Yes | Yes (Reboot) | Low (Select new shape) |
| Bare Metal | No | High | Medium (Recreate Instance) |
| Arm (A1/A2) | Yes | Yes (Reboot) | Low (Stay within Arm family) |
Cross-Architecture: You cannot resize an AMD-based VM to an Arm-based VM. Because the CPU instruction sets are different, the OS wouldn't be able to boot. You must create a new server and migrate your data.
Service Limits: Before resizing to a massive shape (like 64 cores), ensure your account has the "Service Limit" available in that region, or the resize request will fail.
Interface Names: Sometimes, changing a shape can cause the OS to rename network interfaces (e.g., ens3 to ens4). It is a good practice to use "Predictable Network Interface Names" in your OS configuration to avoid losing connectivity.