# WorkSpaces Core Managed Instances now support ModifyVolume, with no restart needed!

Hi everyone, Shii-chan here! Today's update makes storage operations for WorkSpaces Core a lot easier!

## What was announced?

According to AWS What's New, Amazon WorkSpaces Core Managed Instances now supports the ModifyVolume API. It lets you change a volume's size, type, IOPS, or throughput in place.

## The story so far

Previously, changing storage capacity or performance on a deployed managed instance required rebuilding it.

## What changes

You can make the change without detaching the volume or restarting the instance. When you run low on capacity or performance, you can respond without rebuilding.

## Dive Deep

Here are the changes you can make:

- Increase volume size up to 16,384 GiB
- Switch between supported Amazon EBS volume types
- Adjust IOPS for gp3, io1, and io2 volumes
- Modify throughput for gp3 volumes

Other details:

- Idempotency tokens are supported to prevent duplicate changes
- Track progress with the Amazon EC2 `DescribeVolumesModifications` operation
- Available in all AWS Regions where WorkSpaces Core Managed Instances is available
- To get started, call `ModifyVolume` directly, or use it through your WorkSpaces Core partner solution once available

For more, see ModifyVolume in the WorkSpaces Instances API Reference and the limitations in the Amazon EBS User Guide.

## Wrap-up

- WorkSpaces Core Managed Instances now support the ModifyVolume API
- You can change size, type, IOPS, and throughput without detaching or restarting
- Size goes up to 16,384 GiB, IOPS applies to gp3, io1, and io2, and throughput applies to gp3
- Progress is visible through `DescribeVolumesModifications`

This is for operations teams building desktop infrastructure on WorkSpaces Core!
