There'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.
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.html
There'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.