AWS drs: Add arm64 right-sizing and launch configuration errors
Summary
Adds troubleshooting entries for arm64/Graviton right-sizing and launch configuration errors, including IAM permission failures for DescribeInstances and role setup guidance.
Security assessment
The change documents operational troubleshooting for DRS launch errors, including an IAM permission failure for DescribeInstances. It does not describe a fixed vulnerability, incident, or new security feature/best practice.
Evidence
+AWS Elastic Disaster Recovery does not have permission to call `DescribeInstances` for the source Amazon EC2 instance. This error appears only when you change the right-sizing method for an `arm64` source server. Otherwise Elastic Disaster Recovery uses its recommended AWS Graviton instance type.
Diff
diff --git a/drs/latest/userguide/launch-configuration-errors.md b/drs/latest/userguide/launch-configuration-errors.md index 399fff442..cc3facec8 100644 --- a//drs/latest/userguide/launch-configuration-errors.md +++ b//drs/latest/userguide/launch-configuration-errors.md @@ -7 +7 @@ -Error: Instance not launched due to lifecycle stateError: OS BYOL requires Dedicated HostsError: EBS encryption key not foundError: Missing IAM permissions for launchError: Instance store volume device name conflict +Error: Instance not launched due to lifecycle stateError: OS BYOL requires Dedicated HostsError: EBS encryption key not foundError: Missing IAM permissions for launchError: Instance store volume device name conflictError: Basic right-sizing is not supported for arm64Error: In-AWS right-sizing cannot describe the source instanceError: Source instance not found for in-AWS right-sizingError: Source instance type is unavailable in the recovery RegionError: Launch template specifies an x86_64 instance type for arm64Error: Instance requirements exclude arm64 instance typesError: AMI architecture does not match the arm64 sourceError: Invalid arm64 recovery settingsError: Launch-into instance architecture does not match @@ -24,0 +25,18 @@ The following errors occur when launch configuration settings, IAM permissions, + * Error: Basic right-sizing is not supported for arm64 + + * Error: In-AWS right-sizing cannot describe the source instance + + * Error: Source instance not found for in-AWS right-sizing + + * Error: Source instance type is unavailable in the recovery Region + + * Error: Launch template specifies an x86_64 instance type for arm64 + + * Error: Instance requirements exclude arm64 instance types + + * Error: AMI architecture does not match the arm64 source + + * Error: Invalid arm64 recovery settings + + * Error: Launch-into instance architecture does not match + @@ -129,0 +148,135 @@ Use one of the following options to resolve this error: +## Error: Basic right-sizing is not supported for arm64 + +**Error message** + +**`Cannot set BASIC right sizing on source server`source-server-id`. BASIC right sizing is not supported for arm64/Graviton source servers. Use IN_AWS or NONE instead.`** + +**Cause** + +You explicitly set **Active (basic)** right-sizing on an `arm64` source server. + +**Resolution** + +Set right-sizing to **Active (in-aws)** or **Inactive**. If the account default launch settings specify **Active (basic)** right-sizing, AWS Elastic Disaster Recovery applies **Active (in-aws)** right-sizing when it creates an `arm64` source server. + +## Error: In-AWS right-sizing cannot describe the source instance + +**Error message** + +**`Could not apply in-AWS right sizing for source server`source-server-id` because AWS Elastic Disaster Recovery is unable to successfully make the DescribeInstances API call against the source EC2 instance `instance-id`.`** + +**Cause** + +AWS Elastic Disaster Recovery does not have permission to call `DescribeInstances` for the source Amazon EC2 instance. This error appears only when you change the right-sizing method for an `arm64` source server. Otherwise Elastic Disaster Recovery uses its recommended AWS Graviton instance type. + +**Resolution** + +Restore permission to describe the source instance, then retry the launch-settings update. For source servers replicated from another account, create the failback and in-AWS right-sizing roles in the source account. See [Creating the Failback and in-AWS right-sizing roles](./adding-trusted-account.html#trusted-accounts-failback-role). + +## Error: Source instance not found for in-AWS right-sizing + +**Error message** + +**`Could not apply in-AWS right sizing for source server`source-server-id` because source instance `instance-id` was not found in its reported account and region.`** + +**Cause** + +The source Amazon EC2 instance no longer exists in the reported account and Region, or the recorded instance identity is incorrect. For when Elastic Disaster Recovery checks the source instance, see Error: In-AWS right-sizing cannot describe the source instance. + +**Resolution** + +Verify the source account, Region, and instance ID. Restore the source instance or reinstall the agent on the correct instance, then retry. + +## Error: Source instance type is unavailable in the recovery Region + +**Error message** + +**`Could not apply in-AWS right sizing for source server`source-server-id` because source instance type `instance-type` is not available in the recovery region.`** + +**Cause** + +The source Graviton instance type is not offered in the recovery Region. Elastic Disaster Recovery runs this check only in the situations described in Error: In-AWS right-sizing cannot describe the source instance. + +**Resolution** + +Use **Inactive** right-sizing and configure a compatible Graviton type, or keep the right-sizing method unchanged so that Elastic Disaster Recovery selects a Graviton recommendation that is offered in the recovery Region. + +## Error: Launch template specifies an x86_64 instance type for arm64 + +**Error message** + +**`Source server`source-server-id` is an arm64 (Graviton) source, but the launch template specifies instance type '`instance-type`', which is not an arm64 instance type. An aarch64 root volume cannot boot on an x86_64 instance. Use a Graviton instance type (such as c6g, m6g, r6g, c7g, or t4g) in your launch template.`** + +**Cause** + +The launch template pins an `x86_64` instance type for an `arm64` source server. + +**Resolution** + +Select a Graviton instance type that is offered in the recovery location. + +## Error: Instance requirements exclude arm64 instance types + +**Error message** + +**`Source server`source-server-id` is an arm64 (Graviton) source, but the launch template's InstanceRequirements cannot be satisfied by any arm64 instance type. An aarch64 root volume cannot boot on an x86_64 instance. Widen AllowedInstanceTypes to include a Graviton family (for example c6g.*, m6g.*, r6g.*, c7g.*, or t4g.*), or relax the attribute constraints so at least one arm64 instance type qualifies.`** + +**Cause** + +The allowed, excluded, or attribute requirements match no `arm64` instance type offered in the recovery Region. + +**Resolution** + +Widen the allowed instance types or relax the requirements so that they match at least one Graviton type offered in the recovery Region. + +## Error: AMI architecture does not match the arm64 source + +**Error message** + +**`Source server`source-server-id` is an arm64 (Graviton) source, but the AMI '`ami-id`' specified for launch has architecture '`ami-architecture`'. An aarch64 root volume cannot boot from an x86_64 AMI. Use an arm64 AMI, or remove the AMI override to let DRS create an architecture-matched AMI.`** + +**Cause** + +The launch template or usage operation specifies an `x86_64` Amazon Machine Image (AMI) for an `arm64` source server. + +**Resolution** + +Use an `arm64` AMI, or remove the AMI override so that AWS Elastic Disaster Recovery creates an architecture-matched AMI. + +## Error: Invalid arm64 recovery settings + +**Error message** + +**`Action could not be completed. Invalid ARM64 recovery settings:`violations` in the launch configuration template.`** + +**Cause** + +The launch template contains one or more of these violations: + + * **`one of InstanceType or InstanceRequirements is required`** + + * **`instance type '`instance-type`' is not an arm64 (Graviton) type`** + + + + +At launch time, the messages described in Error: AMI architecture does not match the arm64 source and Error: Instance requirements exclude arm64 instance types can also appear inside this error. + +**Resolution** + +Specify a Graviton instance type or satisfiable instance requirements in the launch template. + +## Error: Launch-into instance architecture does not match + +**Error message** + +**`You cannot define the EC2 instance`ec2-instance-id` as a launch into instance ID as is has conflicting instance settings to those of the source server (`source-server-id`). The following fields have a configuration mismatch: Architecture.`** + +**Cause** + +The target instance does not use the same architecture as the protected server. + +**Resolution** + +Select a stopped target Amazon EC2 instance that uses the same architecture as the protected server and meets the other launch-into requirements. +