- 最新
- 最多得票
- 最多評論
Based on the information provided, it appears your c8g.2xlarge instance has become unresponsive despite showing a "running" state and passing status checks. This situation is similar to other cases where instances appear healthy from AWS monitoring perspective but are actually unreachable.
While I can't directly check your specific instance using a physically connected serial console (as this would require AWS Support intervention), I can suggest some troubleshooting steps:
-
The issue might be related to the underlying system rather than broken hardware. Sometimes instances can become unresponsive due to disk errors that cause the filesystem to be mounted in read-only mode, or due to kernel-level issues.
-
Since you mentioned you were running a Docker build process, it's possible that despite having sufficient RAM, there could be other resource constraints or system-level issues triggered by the build process.
-
You could try stopping and starting the instance (not just rebooting) which would migrate it to different underlying hardware.
-
If possible, create a snapshot of the instance's root volume before terminating it, which would allow you to investigate the issue further or recover data if needed.
Regarding your refund request, you would need to contact AWS Support directly to discuss billing adjustments for service issues. They can review your specific case and determine if a refund is appropriate based on their service level agreements.
Sources
statuscheckfailed_instance still unreachable after reboot and shutdown restart | AWS re:Post
