3 ms·
Sort of, but maybe not quite? When you spin up an EC2 spot instance, it's a fresh instance with whatever AMI you load into it, and it's a fresh boot at that ti
by kelnos 10mo ago
Sort of, but maybe not quite? When you spin up an EC2 spot instance, it's a fresh instance with whatever AMI you load into it, and it's a fresh boot at that time. (You can save persistent data to an EBS volume that you create once up front and then attach to each new instance, of course.)
With this service, it seems like the VM underpinning your session is suspended (like as if you were to suspend-to-RAM or hibernate your laptop), and then resumed the next time you sign in, so not only is the filesystem in the same state as it was during your last session, but any background processes that have spun up since then are resumed as well, and are still running.
- electroly 10mo agoEC2 instances can hibernate, too. You stop paying for the instance while it's hibernated; you pay the EBS storage cost only. https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Hibernate.html https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Hibernat...
- TurdF3rguson 10mo agoRight you would need it to be on-demand to hibernate like that but even then a medium will beat these prices I believe.
- arianvanp 10mo agoI think you can technically hibernate the instance when the spot reclaim signal comes in. Then snapshot the instance and then terminate it. Can then spawn a new instance from the snapshot and it should unhibernate Whether the OS will like that... That's another point. As there will be things that change like smbios etc
- TurdF3rguson 10mo agoThat's a cold boot though and things like tmux sessions will disappear. (I'm assuming that doesn't happen with shellbox)