Course contentsShow
← Cloud and Infrastructure
Lesson 89 of 2,9892. Compute FoundationsFree lesson

Instance Resize and Type Changes

How to change VM instance types, downtime requirements, compatibility constraints, and when resizing is appropriate.

Instance Resize and Type Changes

What you'll learn: How to change your VM's size or type after launch, including when it's safe and what to expect during the process.

Why Resize an Instance?

Sometimes your VM's workload changes. Maybe your web application became more popular and needs more memory, or you initially over-provisioned and want to save costs by downsizing. Resizing means switching your VM to a different instance type or size—like upgrading from a t3.small to a t3.large, or changing from a general-purpose type to a memory-optimized one.

How Resizing Works

Think of it like moving to a new apartment: you pack up (stop the VM), move to a bigger or smaller place (change the instance type), then unpack (restart). Most cloud providers require downtime—your VM must be stopped before resizing. The VM's storage volumes stay attached, so your data remains intact, but any in-memory state is lost.

Compatibility Constraints

Not all changes are allowed. You typically can't resize:

  • Between different virtualization types (e.g., older generation to newer without migration)
  • From x86 to ARM architectures
  • To types incompatible with your current operating system or storage configuration

You can usually resize within the same instance family (e.g., m5.large to m5.xlarge) or between compatible families.

When to Resize

Resize when you've consistently observed performance issues or waste for several days. Don't resize based on temporary spikes—use auto-scaling instead. Review metrics like CPU utilization, memory pressure, and disk I/O before deciding.

Key Takeaway: Instance resizing changes your VM's hardware profile but requires stopping the instance and works only between compatible types—plan for downtime and verify compatibility first.