Anomaly Detection
Powered By GitBook
Setting Up Spot Scaling
How to set up and implement Spot Scaling recommendations

Connect your AWS Accounts

To use Spot Scaling, you must provide access to your AWS account(s) to the CMP. Read this article to see how to link your AWS account(s).
If you’ve already linked your AWS account(s) to the CMP, go to this step instead.
As part of linking your account, you will need to create an AWS IAM Role and attach an IAM Policy to it containing a requisite set of permissions. These permissions allow Spot Scaling to function — monitor your ASG behavior, make spot instance recommendations, and allow you to implement them from the CMP
In the same article linked above, read the section on how to create a policy for Spot Scaling with the requisite permissions.

AWS Account previously linked

If your account was already linked prior to enabling Spot Scaling functionality, you need to update the role attached to the account with the additional requisite permissions for Spot Scaling**.**
Follow these instructionson adding a feature to an already-linked AWS account. Be sure to check the box next to "Spot Scaling", as shown below.
A screenshot showing the checkbox next to Spot Scaling

Implement Spot Scaling Recommendations

View Recommendations

To navigate to your Spot Scaling recommendations, click on the Spot Scaling icon in your lefthand navigation panel.
A screenshot showing the location of the Spot Scaling menu item
Once an AWS account is linked, any Auto Scaling Groups (ASGs) associated with it which aren't optimized will appear in your Spot Scaling page.
These ASGs will have a value of "Not Optimized" under the "Optimization Status" column.
A screenshot showing the location of the Optimization Status column
Click on the ASG to view its Spot Scaling recommendation.
A screenshot showing the location of the ASG link
Your ASG's current configuration is displayed under the "Current Values" column. Spot Scaling's recommendations are displayed under the "Recommended Values" column.

Additional Spot Scaling Settings

With Spot Scaling you have two optional features you can turn on when optimizing your ASG's configuration:
    Keep my ASG up to date: If turned on, Spot Scaling will automatically update the ASG's configuration to continuously maximize system runtime and spot-related EC2 savings.
    Fallback to On-Demand: When there aren't where enough unused EC2 instances to meet demand for Spot instances, Spot Scaling will automatically fallback to on-demand instances.
A screenshot showing the location of the General Settings section

ASG Potential Savings Metrics

To better understand your potential savings for each ASG Spot Scaling can optimize, you can see two metrics for each recommendation:
    Monthly Savings Potential: How much Spot Scaling can save you if you apply its recommendation.\
    Monthly Saving Rate: The percentage savings over on-demand you'll realize if you apply Spot Scaling's recommendation.

Apply Recommendations

Examine the recommendations and, if the proposed changes seem satisfactory with you, click on APPLY RECOMMENDATIONS to reconfigure your ASG according to Spot Scaling's recommendations.
A screenshot showing the location of the Apply Recommendations_ button
If you want to tweak the recommendation, you may also modify the values under the following rows before applying it:
    On-Demand Base Capacity
    On-Demand Instances
    Spot Instances
Once you've applied the recommendation, the "Recommended Values" column will disappear.
The values under the "Current Values" column will update, reflecting the changes you made when applying the recommendation.
A screenshot showing the Current Values column
Additionally, once you apply a recommendation, the metrics appearing at the top will update, showing you the previous month's savings and the current month's savings. You will see a breakdown of hours and cost under each metric for both spot and on-demand instances.
Finally, after applying a recommendation, your ASG will see a value of "Optimized" under the "Optimization Status" column.
A screenshot showing an Optimized status under the Optimized Status column
Last modified 6d ago