Cmpute.io is now a part of Cisco. Learn More

About Cisco

Frequently Asked Questions

How can I trust spot instances since they’re prone to termination or if my application is not suited to run on spot instances?

CMPUTE uses historical information and prediction modeling in its bidding strategy and instance selection model. This gives cmpute high retention rates for the spot instances it launches. For e.g., we have data for running a spot instance continuously for more than 30 days without losing it.

Additionally, cmpute continuously monitors the spot instances it launches and if it predicts an increased likelihood of an instance getting terminated, it preempts the termination and swaps the instance with a lower risk spot instance or an on-demand instance without any user intervention or disruption to availability.

Finally, cmpute is not only about spot instances. cmpute uses a combination of On-Demand, Reserved and Spot Instances to ensure a distribution model that gives deep cost savings without compromising on your application uptime.

How can I reliably run my web application on spot instances as it can be terminated at any moment?

CMPUTE provides a 3 level defense mechanism to ensure that you get deep cost savings without compromising on your application availability / uptime.

  • First: cmpute uses historical data and prediction modeling to identify the right bidding strategy and the right instance type in a spot market so that the instances that are launched are not terminated anytime soon.

  • Second: cmpute ’s continuous learning algorithm tracks the spot instances that were launched and preempts a termination by proactively swapping an instance out if the chances of failure are high.

  • Third: cmpute lets users define a “minimum on-demand threshold” that can ensure that a portion of the instance pool is always fulfilled using on-demand instances.

These multiple lines of defense help even web applications to leverage Spot Instances via cmpute , for huge cost savings.

What applications can I use CMPUTE for?

CMPUTE can be used in a wide range of applications:

  • Web apps- Auto Scaling Groups, ELB, Elastic BeanStalk or Custom AMIs
  • Amazon EMR
  • Load Testing with JMeter
  • Video transcoding with FFMPEG
  • Web Crawling, OCR … and many more.

I’m a Cloudability customer. Is CMPUTE a similar solution?

No. cmpute is a solution that delivers cost savings via intelligent use of spot instances. cmpute can work in conjunction with Cloudability where you can track and analyze the performance of cmpute in your Cloudability dashboard.

I have purchased Reserved Instances. How useful will CMPUTE be for me?

CMPUTE has automatic support for RIs. If you have purchased RIs and have them available, cmpute would automatically use them as the first choice. cmpute would start launching spot or on-demand instances only after a partial or full consumption of your RIs ensuring maximum value to your RI spend.

Do I need to add tags for CMPUTE ?

CMPUTE creates default tags for all instances it launches and it also supports the ability to add custom tags.

Should I re-engineer or write code to use CMPUTE ?

No. cmpute has a unique app store model where most common AWS applications are pre-configured to help you get started without any additional coding or IT overhead.

How do you handle glitches and availability? How can I be sure you will move the workload over? What happens when my spot instances get terminated?

CMPUTE uses an algorithm that tends to hold on to the instances it launches. In cases where the spot instances get terminated, cmpute would automatically launch additional instances (in most cases pre-emptively, before the termination) and keep your application running without any intervention from your end.

Is there no way to define a more specific SLA? e.g. I need my app to have 99.99% uptime?

When you actually configure your app in cmpute , you can specify your distribution between On-demand and Spot instances. We use following three line defense strategy so that you can have guaranteed uptime:

The ability to retain the spot instances we launch for much longer than norm using our predictive algorithm. Continuously monitoring the instances and swapping out high risk instances automatically. Fulfilling a portion of the Auto Scaling Group via On-demand instances. This ensures that you don’t have to worry about spot termination and uptime issues. With this approach, you can achieve uptime levels similar to what you’d currently be getting on AWS.

How do I get started with CMPUTE ?

You can sign up for an account here and get started immediately by adding a AWS IAM Role ARN.

What do I need to install?

CMPUTE is a SaaS solution that doesn’t require the installation of any components. cmpute creates an AWS Role Amazon Resource Name (ARN) that is completely transparent and works in your account to balance and tune workloads. Click here to see details.

How does auto scaling work with CMPUTE ? Is it the same as AWS’ auto scaling?

Yes. It is similar. We use the same Auto Scaling configuration and start managing the Auto Scaling Group via cmpute .

Can I specify that I need the instances to be in a specific region?

Yes. While configuring the application, you can specify the region where you want the instances to be launched.

Are on-demand instances always run just in case all of my spot instances get terminated?

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.

Do I need to enter the minimum number of on-demand instances I want in order to guarantee my uptime?

Yes.

Does CMPUTE automatically kill spot instances that fail their health checks while still maintaining the minimum number of on-demand instances I specified?

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.

Do I specify some thresholds about when I want the scaling to occur and when a threshold is hit, the group is scaled?

Yes.

Does CMPUTE choose whether the instance that gets spun up is spot or on-demand? Or is it always spot?

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).

What exactly is a high risk instance? Just an instance that does not pass its health checks?

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.

How secure is CMPUTE ?

From using a CloudFormation template for creating a role to storing all user account information in encrypted format and using HMAC-SHA1 authentication, cmpute takes security seriously at every step.

Should I share my AWS keys with CMPUTE ?

No. cmpute doesn’t require your AWS keys and uses a transparent AWS IAM Role ARN approach to manage your AWS environment.

How do I get started with CMPUTE ?

You can sign up for an account here and get started immediately by adding a AWS IAM Role ARN.

What do I need to install?

CMPUTE is a SaaS solution that doesn’t require the installation of any components. cmpute creates an AWS Role Amazon Resource Name (ARN) that is completely transparent and works in your account to balance and tune workloads. Click here to see details.