OS patching and upgrades with Amazon EC2 root volume replacement
Compute Blog
This article explains how to use Amazon EC2 Replace Root Volume (RRV) to patch and upgrade operating systems on stateful workloads while preserving instance identity, IP addresses, and attached resources.
- Prepare and validate replacement root volumes on separate instances before swapping onto production
- Swap volumes with a single API call, limiting downtime to one reboot plus application restart time
- Preserve instance ID, private/public IP addresses, ENIs, data volumes, IAM profiles, and security groups during replacement
- Supports rollback by keeping original root volume or using snapshots as fallback
- For Auto Scaling groups, use Standby mode for one-at-a-time updates or instance refresh with ReplaceRootVolume strategy for fleet-wide updates
- Requirements include same Availability Zone, matching encryption, compatible boot mode, and ENA/NVMe drivers for Nitro instances
RRV reduces OS upgrade downtime and complexity by eliminating resource re-association steps required with traditional instance replacement.
The AWS News Feed is currently looking for gold sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.
Related articles
Jul 10
2026
2026
Amazon EC2 now supports using an EBS volume for Replace Root Volume
Nov 20
2025
2025
Amazon EC2 Auto Scaling now supports root volume replacement through instance refresh
Sep 16
2026
2026
Amazon ECS extends Amazon S3 Files support to the Amazon EC2 compute type
May 28
2025
2025
AWS Backup enhances Amazon EC2 restores with custom volume configuration support
The AWS News Feed is currently looking for silver sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.