A company has an SAP Business One system that runs on SUSE Linux Enterprise Server 12 SP3. The company wants to migrate the system to AWS. An SAP solutions architect selects a homogeneous migration st

Rebooting the instance does not resolve missing OS-level drivers; the instance will continue to fail status checks on any host because the problem exists within the guest operating system itself, not the underlying EC2 hardware.

An instance limit increase is the appropriate action when AWS prevents launching an instance due to service quotas, not when an already-launched instance fails internal status checks and refuses network connections due to driver issues.

AWS Support cannot install or remediate missing drivers inside a customer's EC2 guest OS; OS-level driver installation is the customer's responsibility and this approach would introduce unnecessary delay without resolving the underlying cause.

R5 instances require the Elastic Network Adapter (ENA) driver for enhanced networking and NVMe drivers for EBS storage access, which are typically not present on a physical server running SUSE Linux Enterprise Server 12 SP3. Installing these required drivers on the source system before the next replication cycle allows CloudEndure to replicate the updated OS state, and relaunching the test instance after synchronization completes will resolve both the status check failures and the refused network connections.