Today, AWS announces Replace Root Volume using an existing EBS volume, a new option for replacing the root volume of a running Amazon EC2 instance. Customers can now use an EBS volume as the target for a root volume replacement, in addition to the existing options of replacing from a snapshot or an AMI. This option supports customers running stateful workloads who need to include specific metadata or software on the root volume before the application boots.
Many customers use Replace Root Volume today to apply operating system patches and configuration changes without stopping the instance. However, customers who needed specific metadata or software on the root volume had to first capture an volume with data as a snapshot or register it as an AMI before they could replace the root volume. These intermediate steps added time and operational overhead. Customers can now configure the volume directly and use it as the new root volume, removing the snapshot and AMI creation steps. This reduces operational overhead and speeds up root volume patching for stateful workloads where downtime is costly.
Using an EBS volume when replacing a root volume of an EC2 instance is available in all commercial AWS Regions and AWS GovCloud (US) regions. To get started, see Replace an EC2 instance root volume in the Amazon EC2 User Guide.
Categories: marketing:marchitecture/compute,general:products/aws-govcloud-us,general:products/amazon-ec2
Source: Amazon Web Services
Latest Posts
- Amazon EC2 network/EBS instances now available in additional regions
- Amazon EC2 G7 instances are now available in the AWS US East (N. Virginia) Region
- AWS Organizations now applies account departure security controls by default for new organizations created via AWS Organizations console
- Amazon EC2 now supports using an EBS volume for Replace Root Volume
