status fail -Launch instance from AMI

Instance status check failure indicates a problem with the instance, such as:

1. Incorrect networking or startup configuration
2. Exhausted memory
3. Corrupted file system
4. Incompatible kernel

The issue you are experiencing with your instance failing to launch from your AMI appears to be related to network configuration problems.

From the error message "Network interface configuration is empty...waiting for an IP..." it could be the issue with Network interface card being disabled or having a static IP assigned to the adapter. To resolve this issue follow below action plan

Action plan:

Attaching a secondary Elastic Network Interface (ENI) with associated Elastic IP (EIP) to the affected instance. To do so please follow the steps outlined below and refer to documentations linked below.

Create an ENI

1. Open the EC2 Console
2. In the left navigation pane select Network Interfaces > Create Network Interfaces
3. Give it the description of 'Helper', select the same subnet as your affected instance and enter the primary private IPv4 address of the instance (will appear in dropdown) or allow Amazon to pick an available one from the subnets specified range.
4. Select the same Security Group as the instance is already in.
5. Choose create.

Attach this ENI to your affected instance

1. Open the EC2 Console
2. In the navigation pane, choose Instances.
3. Choose Actions > Networking > Attach Network Interface.
4. In the Attach Network Interface dialog box, select the network interface named 'Helper' > choose Attach.

After you create the secondary interface, you can try and connect to the IP address associated with the secondary interface, once you are connected open the network settings (ncpa.cpl) inside the os and enable the primary ethernet adapter if disabled or fix the changes made there.

[+] Create a temporary elastic network interface

[+] Instance status checks