Skip to content

Latest commit

 

History

History

total_instance_vcpus_forecast

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
CHANGELOG.md
CHANGELOG.md
 
 
README.md
README.md
 
 
aws_usage_forecast_instance_vcpus_used.pt
aws_usage_forecast_instance_vcpus_used.pt
 
 

README.md

AWS Usage Forecast - Number of Instance vCPUs Used

Deprecated

This policy is no longer being updated. The AWS Usage Forecast - Instance Time Used policy now includes this functionality and should be used instead.

What It Does

This Policy leverages Flexera CCO APIs to determine a usage forecast for a view of AWS instance vCPUs used within the entire Organization. The policy uses the specified previous number of months, not including the current month to to determine a straight-line forecast using a linear regression model.

How It Works

  • This policy uses the last month before current to guarantee full data.
  • This policy supports filtering by a specific AWS region or the entire Organization.
  • This policy produces a straight-line forecast by calculating a line of best fit (linear regression line) from the historical dataset and then extrapolating this to calculate forecasted costs.
  • The forecast is displayed as a stacked-bar chart showing Total Instance vCPUs by Instance Family for the top 8 most used Instance Families. All other Instance Families will be aggregated and displayed as "Other". Values shown in the graph are for the past 12 months.

Input Parameters

This policy has the following input parameters required when launching the policy.

  • Region - Name of the AWS Region to filter by. Example: 'US West (Oregon)'. Leave this blank for 'Organization' scope.
  • Lookback Months - Number of months to lookback to generate forecast.
  • Months to forecast - Number of months in the future to forecast.
  • Email addresses to notify - A list of email addresses to notify.

Policy Actions

  • Sends an email notification

Prerequisites

This Policy Template uses Credentials for authenticating to datasources -- in order to apply this policy you must have a Credential registered in the system that is compatible with this policy. If there are no Credentials listed when you apply the policy, please contact your Flexera Org Admin and ask them to register a Credential that is compatible with this policy. The information below should be consulted when creating the credential(s).

Credential configuration

  • Flexera Credential (provider=flexera) which has the following roles:
    • billing_center_viewer

The Provider-Specific Credentials page in the docs has detailed instructions for setting up Credentials for the most common providers.

Supported Clouds

  • AWS

Cost

This policy template does not incur any cloud costs.