-
16 virtual cores. What that means in reality, I don't know. I'm not a CPU guy. But 16 is more than 8 and 8 is more than 4... you get the point.
"Each vCPU is a thread of a CPU core, except for T2 instances and 64-bit ARM platforms such as instances powered by AWS Graviton2 processors and Apple Silicon Mac instances."
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-optimize-cpu.htmlThere's instance storage which dies when the instance dies. Don't think you can do things like snapshot it and reattach it to another instance, new instance, etc. We don't use servers with this, only EBS.
EBS volumes persist if the instance is stopped, but not if it is terminated.
You can stop an instance and then you just pay for the volume storage. You can snapshot an instance and terminate it kill its volumes and then restore it later from the snapshot. You will pay to store the snapshot(s) but obviously not as much as leaving an instance running.
-
EBS volumes persist if the instance is stopped, but not if it is terminated.
You can stop an instance and then you just pay for the volume storage. You can snapshot an instance and terminate it kill its volumes and then restore it later from the snapshot.
OK thanks, this sounds useful. Hopefully it will start to make sense to me soon.
Think I might start another account with free tier (looked at this over a year ago and then gave up) so I have some storage to play with initially.
Trying to wrap my head around the process and potential cost of using AWS (Nimble Studio) for hobby-ist 3D modelling/rendering, kind of as a test-bed for taking on some freelance work in lieu of a workstation of my own.
When AWS say 16vCPU does that mean something equivalent to a 16 core CPU?
Also some of the EC2 instances seem to come with some amount of local storage, presumably anything written to these is wiped when you give it up and must be copied to some additional paid storage somewhere?scrap that, I see it's an option whether to have it persist or not.