- Newest
- Most votes
- Most comments
AWS Cloud9 environments should hibernate after a period of inactivity if they are set to do so. In your case, it's set to hibernate after 30 minutes of inactivity. However, there could be several reasons why the environment is not hibernating as expected:
-
Activity Detection: AWS Cloud9 detects activity based on both editor and terminal usage. If there's any activity in either of these (like a running process in the terminal), the environment might not hibernate.
-
Automated Processes: If you have any automated processes running in your environment (like cron jobs), they could be keeping your environment active.
-
Connected Services: If your Cloud9 environment is connected to other AWS services that are constantly interacting with it, it could be keeping your environment from hibernating.
In order to debug this issue, you could try the following:
-
Check Running Processes: Check if there are any running processes in your environment. You can do this by running the
ps
command in the terminal. -
Review Logs: Review the logs to see if there are any errors or messages related to hibernation.
-
Contact AWS Support: If you are unable to resolve the issue yourself, you could consider contacting AWS support for assistance. They may be able to provide more insight into what's happening.
Relevant content
- asked a year ago
- asked 2 years ago
- asked 5 months ago
- asked 5 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 3 years ago