Yes. It is similar. We use the same Auto Scaling configuration and start managing the Auto Scaling Group via cmpute .
Yes. While configuring the application, you can specify the region where you want the instances to be launched.
It is a choice you have. For low risk applications (like Dev / QA), you can have a full spot strategy. For prod workloads, you can go with a hybrid approach. All instances launched by cmpute will be tagged. You can track and trace everything that cmpute does from your AWS Management Console.
Yes. cmpute does that. Not just spot instances, but even the On-demand or Reserved Instances that cmpute launches, if they fail the health checks. You will receive notifications of all such activity.
CMPUTE will first use Reserved Instances if they are available in your account. It will then go in for spot instances and use On-Demand instances as the last option. It will always adhere to any provisioning rules defined by you (e.g. minimum no. of on-demand instances).
High risk instance is a spot instance that is predicted by cmpute to be terminated by AWS soon. The termination risk for a spot instance launched by cmpute can increase over time and when cmpute estimates the risk to be high, it proactively replaces it.