- Newest
- Most votes
- Most comments
Hi. Changing to bigger instance type or extending EBS volume size from EC2 console will not work?
If so, creating new Cloud9 environment, detach EBS volume from existing Cloud9 instance, attach&mount new EBS volume, to Cloud9 new instance and copy data from existing one will work.
Thanks for your quick response. I'm using m5.large. I doubled the size of EBS (it looks like I don't have to resize2fs), but that didn't solve the problem. It's doing the same thing.
I've increased the size of the instance from m5.large to m5.2xlarge and it's still doing the same reload count down to reloading the IDE. This makes the IDE impossible to use.
I'm afraid but you had better recreate environment and salvage data.
detach EBS volume from existing Cloud9 instance, attach&mount new EBS volume,
The procedure of this is here.
Relevant content
- Accepted Answerasked 3 years ago
- Accepted Answerasked 2 years ago
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
I encountered the same issue. Were you able to resolve it? Cloud9 was a good product while it was working.