AWS drs: DRS launch settings: arm64 right-sizing and boot mode requirements
Summary
Adds a note that Active (basic) right-sizing is not available for arm64 source servers, clarifies that failback and in-AWS right-sizing roles must exist in the source account for cross-account replication, and updates instance launch prerequisites to cover UEFI/BIOS boot modes and processor architecture (x86_64/arm64).
Security assessment
The change is primarily about arm64 support and launch prerequisites. It mentions IAM roles for cross-account replication but only as a functional prerequisite, not as a security fix or hardening guidance.
Evidence
+ * If you select the **Active (in-aws)** option, AWS Elastic Disaster Recovery will periodically update the EC2 launch template based on the hardware configuration of the EC2 instance source server. For source servers replicated from another account, the failback and in-AWS right-sizing roles must exist in the source account. Otherwise, Elastic Disaster Recovery uses the recommended instance type. See [Creating the Failback and in-AWS right-sizing roles](./adding-trusted-account.html#trusted-accounts-failback-role).
Diff
diff --git a/drs/latest/userguide/launch-general-settings.md b/drs/latest/userguide/launch-general-settings.md index 0fd491646..198b10e79 100644 --- a//drs/latest/userguide/launch-general-settings.md +++ b//drs/latest/userguide/launch-general-settings.md @@ -49 +49,5 @@ The DRS launch settings include the following parameters: - * If you select the **Active (in-aws)** option, AWS Elastic Disaster Recovery will periodically update the EC2 launch template based on the hardware configuration of the EC2 instance source server. +###### Note + +If your default launch settings use **Active (basic)** , Elastic Disaster Recovery applies **Active (in-aws)** to new `arm64` source servers. You cannot select **Active (basic)** for an `arm64` source server. + + * If you select the **Active (in-aws)** option, AWS Elastic Disaster Recovery will periodically update the EC2 launch template based on the hardware configuration of the EC2 instance source server. For source servers replicated from another account, the failback and in-AWS right-sizing roles must exist in the source account. Otherwise, Elastic Disaster Recovery uses the recommended instance type. See [Creating the Failback and in-AWS right-sizing roles](./adding-trusted-account.html#trusted-accounts-failback-role). @@ -117 +121,7 @@ The launch into an instance will fail if the following pre-requisites are not me - 4. If the instance to launch into is a Linux it must have the BIOS boot mode, and if Windows it must have the same boot mode as that of the server it is protecting. + 4. The instance to launch into must support the boot mode of the server it is protecting. If the protected server uses the UEFI boot mode, the instance to launch into must also use the UEFI boot mode. If the protected server uses the legacy BIOS boot mode, the instance to launch into can use either boot mode. This applies to both Linux and Windows. + + 5. The instance to launch into must meet these requirements: + + * The same processor architecture as the source server: `x86_64` or `arm64`. + + * Hardware virtual machine (HVM) virtualization. @@ -119 +129 @@ The launch into an instance will fail if the following pre-requisites are not me - 5. The instance to launch into must have the x86_64 architecture, HVM virtualization and an EBS root device. + * An Amazon Elastic Block Store (Amazon EBS) root device.