AWS c9 environment won't open - all trouble shooting documents consulted

Question

I was developing in c9 on an ec2 t3 instance, everything fine and well for a few months until yesterday and I cannot get into my cloud9 environment again.  
  
The error that pops up:  
  
"This is taking longer than expected. The delay may be caused by high CPU usage in your environment, or your T2 or T3 instance is running out of burstable CPU capacity credits, or there are VPC configuration issues. Please check documentation."  
  
I have consulted the troubleshooting documents. I have not touched the VPC settings at all, and cannot see/find any irregularities in the VPC settings. Moreover, I have changed the instance type 3 times now, and is currently on an M4.large instance type - the issue still occurs and the same error message pops up.   
  
I think the issue may be related to vCPU credits or something? Do I need to purchase more credits? Or is this related to those burstable credits? I'm kindly looking for an explanation in layman terms as to why this is happening, and how do I fix it so that it does not occur in the future. I'm still fairly new to AWS and to consult the documentation does no help and goes over my head.   
  
Thanks in advance to any help or response

Answer

For future reference and people having the same issue - to fix my solution, I had to create a Capacity Reservation for the specific instance. I am still not sure if this is the correct/best method for fixing the issue as the documentation is still unclear to a layman. Moreover, the pricing is not very straight forward. In my perspective, the price is double fold on the instance, e.g. an instance that runs $0.45 an hour results in the capacity costing $0.45 an hour. Maybe if an Amazonian can confirm this it would be greatly appreciated.

AWS c9 environment won't open - all trouble shooting documents consulted

Relevant content