To make this even more streamlined you'd tag the volumes and discover the volumes with `aws ec2 describe-volumes` and filter unattached volumes with the magic tag.
Persisting state between AWS EC2 spot instances
11–20 of 80 posts
Re: Persisting state between AWS EC2 spot instances
#12If you don't care about reliability, why not just get a cheap and powerful VPS? Paying $90/month for that machine is madness. I pay $6/month for 6GB RAM, 4 cores, 50GB disk.
Where? I'm using Digital Ocean and it'd be way more expensive for that kind of configuration.
Digital Ocean is still a premium provider.
I would look at providers like OVH and even cheaper (Treudler, TransIP, RamNode, etc.) For example, an SSD with 2 vCPUs, 8GB RAM and 40GB SSD is 13.49$ per month from OVH.
Re: Persisting state between AWS EC2 spot instances
#13If you don't care about reliability, why not just get a cheap and powerful VPS? Paying $90/month for that machine is madness. I pay $6/month for 6GB RAM, 4 cores, 50GB disk.
Where? I'm using Digital Ocean and it'd be way more expensive for that kind of configuration.
Here’s a list of providers by cost:
(PS: Don’t use DigitalOcean, they tend to steal your credit if they feel like it. Lost 100 bucks "promotional credit" that way with only a few days notice)
Re: Persisting state between AWS EC2 spot instances
#14Earlier quoted context omitted.
Where? I'm using Digital Ocean and it'd be way more expensive for that kind of configuration.
Here’s a list of providers by cost: https://git.io/vps (PS: Don’t use DigitalOcean, they tend to steal your credit if they feel like it. Lost 100 bucks "promotional credit" that way with only a few days notice)
They expired some credits that I haven't used but after asking they just restored them and I could use them. Asking helps.
Re: Persisting state between AWS EC2 spot instances
#15Wouldn't it be simpler to have the smallest possible instance run an NFS server? This would also have an additional bonus of scalability. Edit: or use AWS EFS
EFS is far more expensive than EBS. Price it out; you'll see.
Re: Persisting state between AWS EC2 spot instances
#16we use k8s at work. i just have to create PVC and when spot instance terminated along with the container; new container will be created and mount the PVC again automatically.
Re: Persisting state between AWS EC2 spot instances
#17Even if you don't use spot instances, the technique of using separate EBS volumes to hold state is useful (and well-known). Ordinary on-demand instances can also be terminated prematurely due to hardware failure or other issues, so storing state on a non-root volume should be considered a best current practice for any instance type.
Re: Persisting state between AWS EC2 spot instances
#18Earlier quoted context omitted.
Here’s a list of providers by cost: https://git.io/vps (PS: Don’t use DigitalOcean, they tend to steal your credit if they feel like it. Lost 100 bucks "promotional credit" that way with only a few days notice)
They expired some credits that I haven't used but after asking they just restored them and I could use them. Asking helps.
Asking is not a solution.
This is a question of trust. I have to trust that DO will keep my data safe, that, if the US government would be after my data, DO would prevent them from accessing it. I have to trust that DO won’t access my data.
How am I supposed to trust my, and my user’s personally identifying data, to a company that just like that revokes credit, without warning, and says "well, if you ask nicely, you can get it back"?
Re: Persisting state between AWS EC2 spot instances
#19If you don't care about reliability, why not just get a cheap and powerful VPS? Paying $90/month for that machine is madness. I pay $6/month for 6GB RAM, 4 cores, 50GB disk.
If you don't care about reliability, why not just get a cheap and powerful VPS?
Personally, because my needs aren't constant. I might need two cores for two months followed by 100 cores for a week.