[REQ HELP] Impaired volume on EC2 instance

Question

I have an EC2 on demand instance (i-0ee5714681de8a73d) which became unresponsive and cut me out from SSH access.  
I tried restarting, stopping & starting but it's stuck on pending status, and it shows an alert saying that the EBS volume (vol-0c70b95bfc2a99080) is impaired.  
  
I managed to stop the instance with AWS CLI, however every attempt to restart it ends with the above outcome.  
When the instance is stopped, I cannot even take a snapshot of the volume, which fails without giving a meaningful error, just a generic:  
API error message  
An internal error has occurred  
  
According to the EC2 dashboard, however the volume status is OK  
  
Can you help me?  
  
Kind regards,  
GP

Answer

We are facing the same issue today. I suppose it's global amazon problem for eu-west-2 Region:  
`  
Instance Connectivity  
  
We are experiencing instance connectivity issues in a single Availability Zone (euw2-az3) in the EU-WEST-2 Region.  
  
We're continuing to address connectivity issues to impacted instances in a single Availability Zone (euw2-az3) in the EU-WEST-2 Region. Services that use EC2 and EBS including Elastic Load Balancing, EFS, Elasticache, ECS Fargate, Sagemaker and ELB, are also impacted.  
  
We're continuing to address connectivity issues to impacted instances in a single Availability Zone (euw2-az3) in the EU-WEST-2 Region. We are experiencing elevated error rates for new instance launches in the impacted Availability Zone. Services that use EC2 and EBS including Connect, EFS, Elasticache, ECS Fargate, Managed Streaming for Apache Kafka and Sagemaker are also impacted.  
  
We're continuing to address connectivity issues to impacted instances in a single Availability Zone (euw2-az3) in the EU-WEST-2 Region. We are starting to see recovery for new instance launches in the impacted Availability Zone. Services that use EC2 and EBS including EFS, Elasticache, ECS Fargate, Managed Streaming for Kafka, EMR and Sagemaker are also impacted. Between 3:02 AM and 5:20 AM PST, Amazon Connect customers experienced degraded call and Chat connectivity and handling for agents in the EU-WEST-2 Region. Amazon Connect issues have been resolved and the service is operating normally.  
`  
  
Edited by: nislupko on Feb 1, 2021 7:37 AM

Answer

@nislupko  
  
It seems that was the issue.   
Thanks for your answer!  
  
GP

[REQ HELP] Impaired volume on EC2 instance

Relevant content