resize-volume
Last updated
Grow the disk of a running service instance. The chosen EBS volume is enlarged via ModifyVolume, then the instance is rebooted so its guest filesystem expands into the new space.
Two volumes can be grown:
root — the boot/OS volume (/dev/xvda). cloud-init grows the root filesystem automatically on the reboot.
data — the /home/rumi data volume (/dev/sdb), where the agent and application content live. cloud-init does not grow secondary volumes, so the instance's boot-time filesystem-grow expands it on reboot.
EBS volumes can only be grown, never shrunk, and AWS enforces a ~6-hour cooldown between modifications of the same volume. Growing to a size the volume already meets or exceeds is a no-op.
rumi cloud aws resize-volume \
--profile <profile> \
--network <network> \
--name <instance> \
--volume <root|data> \
--size <GiB> \
[options]--profile
-p
AWS profile to use
Required
--region
-r
AWS region
us-east-1
--network
-n
Name of the network the instance is in
Required
--name
-a
The name of the service instance to resize
Required
--volume
-d
Which volume to grow: root (boot/OS) or data (/home/rumi)
Required
--size
-s
The new volume size in GiB (grow-only)
Required
--no-wait
-o
Whether to not wait for the instance to fully restart
false
Grow the /home/rumi data volume of instance w1 to 40 GiB:
Grow the root volume to 16 GiB:
resize-instance — change the EC2 instance type (CPU/RAM), not the disk
attach-volume — attach a new, additional volume
Last updated
rumi cloud aws resize-volume \
--profile my-aws-profile \
--network my-network \
--name w1 \
--volume data \
--size 40rumi cloud aws resize-volume \
--profile my-aws-profile \
--network my-network \
--name w1 \
--volume root \
--size 16