Is it possible to automatically stop idle dev environments?
As per the title, is it possible for dev environments to automatically shutdown when not being used (or do they already do this and I haven't noticed)
I setup a codecatalyst space to investigate usage last week and it's showing that I've exceeded the free tier - at most I've used maybe 10-15 hours actively.
- Newest
- Most votes
- Most comments
It looks like the Cloud9 tab was left open. We have updated our documentation to reflect what needs to be done:
A Dev Environment will not timeout if any instances including web browsers, remote shells, and IDEs remain connected, so make sure to close all connected instances to avoid incurring additional costs.
https://docs.aws.amazon.com/codecatalyst/latest/userguide/devenvironment-stop.html
You might want to check and modify the value of the Timeout field in your development environment.
As reported in the documentation:
A Dev Environment will automatically stop if it is idle for the amount of time that was selected in the Timeout fields during Dev Environment creation. You can stop the Dev Environment before it goes idle. If you chose No timeout when you created your Dev Environment, the Dev Environment will not stop automatically. Instead, it will run continuously.
https://docs.aws.amazon.com/codecatalyst/latest/userguide/devenvironment-stop.html
Thanks for that @MassimilianoAWS, I've looked at this and I can see this in my dev environments:
So as you can see, I've not touched the dev environment for 3 hours or so, but even though it has a timeout of 15 mins, the status is still running.
Thanks for bringing the issue to our attention. We are taking steps to resolve the issue and will get back to you soon.
Relevant content
- Accepted Answerasked a year ago
- Accepted Answerasked a year ago
AWS OFFICIALUpdated 2 years ago- AWS OFFICIALUpdated 11 days ago
- AWS OFFICIALUpdated 22 days ago
- AWS OFFICIALUpdated 2 years ago
@rahul_aws, I've tried my earlier tests where I'd left a browser tab open in the IDE by making sure I'd closed them all down, and the environments all shutdown as expected.
Can we not also shut down the Cloud9 instance after a specific time of inactivity if there is no action in the browser tab?