Troubleshoot an unreachable Amazon EC2 instance
The following information can help you troubleshoot unreachable Amazon EC2 instances. You can capture screenshots or access console output to help diagnose problems and determine if you should reboot your instance. For unreachable Windows instances, troubleshoot by reviewing screenshots returned by the service.
Contents
Instance reboot
The ability to reboot instances that are otherwise unreachable is valuable for both troubleshooting and general instance management.
Just as you can reset a computer by pressing the reset button, you can reset EC2 instances using the Amazon EC2 console, CLI, or API. For more information, see Reboot your instance.
Instance console output
Console output is a valuable tool for problem diagnosis. It is especially useful for troubleshooting kernel problems and service configuration issues that could cause an instance to terminate or become unreachable before its SSH daemon can be started.
-
Linux instances – The instance console output displays the exact console output that would normally be displayed on a physical monitor attached to a computer. The console output returns buffered information that was posted shortly after an instance transition state (start, stop, reboot, and terminate). The posted output is not continuously updated; only when it is likely to be of the most value.
-
Windows instances – The instance console output includes the last three system event log errors.
Only the instance owner can access the console output.
You can retrieve the latest serial console output during the instance lifecycle. This option is only supported on Nitro-based instances.
Capture a screenshot of an unreachable instance
If you are unable to connect to your instance, you can capture a screenshot of your instance and view it as an image. The image can provide visibility as to the status of the instance, and allows for quicker troubleshooting.
You can generate screenshots while the instance is running or after it has crashed. The image is generated in JPG format and is no larger than 100 kb. There is no data transfer cost for the screenshot.
Limitations
This feature is not supported for the following:
-
Bare metal instances (instances of type
*.metal
) -
Instance is using an NVIDIA GRID driver
-
Windows instances on AWS Outposts
-
Windows instances on AWS Local Zones
Supported Regions
This feature is available in the following Regions:
-
US East (N. Virginia) Region
-
US East (Ohio) Region
-
US West (N. California) Region
-
US West (Oregon) Region
-
Africa (Cape Town) Region
-
Asia Pacific (Hong Kong) Region
-
Asia Pacific (Hyderabad) Region
-
Asia Pacific (Jakarta) Region
-
Asia Pacific (Melbourne) Region
-
Asia Pacific (Mumbai) Region
-
Asia Pacific (Osaka) Region
-
Asia Pacific (Seoul) Region
-
Asia Pacific (Singapore) Region
-
Asia Pacific (Sydney) Region
-
Asia Pacific (Tokyo) Region
-
Canada (Central) Region
-
Canada West (Calgary) Region
-
China (Beijing) Region
-
China (Ningxia) Region
-
Europe (Frankfurt) Region
-
Europe (Ireland) Region
-
Europe (London) Region
-
Europe (Milan) Region
-
Europe (Paris) Region
-
Europe (Spain) Region
-
Europe (Stockholm) Region
-
Europe (Zurich) Region
-
Israel (Tel Aviv) Region
-
South America (São Paulo) Region
-
Middle East (Bahrain) Region
-
Middle East (UAE) Region
Instance recovery when a host computer fails
If there is an unrecoverable issue with the hardware of an underlying host computer, AWS may schedule an instance stop event. You are notified of such an event ahead of time by email.
To recover an Amazon EBS-backed instance running on a host computer that failed
-
Back up any important data on your instance store volumes to Amazon EBS or Amazon S3.
-
Stop the instance.
-
Start the instance.
-
Restore any important data.
For more information, see Stop and start Amazon EC2 instances.
To recover an instance store-backed instance running on a host computer that failed
-
Create an AMI from the instance.
-
Upload the image to Amazon S3.
-
Back up important data to Amazon EBS or Amazon S3.
-
Terminate the instance.
-
Launch a new instance from the AMI.
-
Restore any important data to the new instance.