Instances that have been suspended or stopped can be shelved after two (2) weeks in said state.
Shelved images/instances will be deleted after six (6) months of inactivity
All entities owned by a project will be deleted 6 months after an allocation ends; , e.g. running instances, images, objects, volumes, networks, IPs allocated etc.
NOTE: If you are using a community-contributed image (i.e. non-Featured image) that belongs to another Atmosphere user, if that user no longer has an allocation or is removed for other reasons, their image will go away as well! If your work is dependent on someone else's image, you might consider making your own version using the instructions Customizing and saving a VM
This includes EAR sanctioned countries and countries under heightened restrictions, as well as definitions for fundamental research
As stated in the XSEDE Usage Policy, users of the Jetstream system are expected to abide by policies established by the service providers.
Acceptable Usage Policies for Jetstream-hosted Gateways - this also includes a link to a sample AUP you should consider implementing for your gateway
Periodically apply operating system updates to your running VMs:
The Ubuntu 20.04, 18.04, 16.04 and Centos 7 featured images are utilizing unattended security updates. Instances will not reboot, but they will apply any update marked as a security update. It's still a good idea to update your VM, just in case.
CentOS: sudo yum update
Ubuntu: sudo apt-get update then sudo apt-get upgrade
If the kernel or glibc/libc packages are being updated, rebooting is necessary to implement those updates
Always run updates before requesting a new custom image in Atmosphere
An actively updating instance may be slow to deploy and may require a redeploy or even a reboot after updating in order to fully successfully deploy.
Remember to logout from the menu at the top right (where it shows your username).
This ensures that you do not inadvertently allow others to access your Jetstream account.
Update and configure software that utilizes the network to preclude unauthorized access.
Commonly neglected examples include MongoDB.