Cost Policies

Gathers Burst Credit and AWS CloudWatch CPU data for EC2 instances on 30-day intervals.

Checks for newly purchased AWS Marketplace products and reports on them.

Checks for snapshots older than specified number of days and, optionally, deletes them.

Sends email notifications when utilization falls below a threshold.

Checks for EC2 instances that have inefficient utilization for a specified number of days and downsizes or terminates them after approval.

Scans all S3 buckets and reports if they don’t have intelligent tiering enabled.

Sends email notifications when AWS Savings Plan Utilizations are identified.

Enables you to schedule start and stop times for your instance, along with the option to terminate instances, update and delete schedules.

Checks all classic load balancers to determine if any are unused (have no healthy instances). Then, you can approve the classic load balancers to be deleted.

Note:Elastic Load Balancing (ELB) supports three types of load balancers: Application Load Balancers, Network Load Balancers, and Classic Load Balancers. This policy only reports on Classic Load Balancers.

Checks for unused volumes and if no read/write operations are performed within a specified number of days, optionally, deletes them.

Automatically takes billing data for Azure China and sends the data to Flexera CBI, so that Azure China costs are visible in Flexera One.

Identifies Linux instances eligible for the Azure hybrid use benefit.

Identifies Windows instances eligible for the Azure hybrid use benefit.

Checks for snapshots older than specified number of days and, optionally, deletes them.

Sends email notifications when utilization falls below a threshold.

Checks for instances that have inefficient utilization for the last 30 days and downsizes or deletes them after approval.

Checks for oversized NetApp capacity pools and suggests recommendations for rightsizing the capacity pools and volumes to optimize efficiency and reduce costs.

Checks for Synapse dedicated SQL pools instances that have inefficient utilization for the user-specified number of days and pauses them after approval.

Calculates savings realized by Reserved Instance purchases for Azure.

Checks a list of Azure SQL Servers and checks for Elastic DB Pools.

Checks for Azure instance types that have been superseded and, optionally, updates the instance type.

Checks for unused volumes older than specified number of days and, optionally, deletes them.

Creates a monthly budget alert for a cloud vendor account.

Specifies which regions have cheaper alternatives by specifying the expensive region name and the cheaper region name for analysis.

Pulls the cost data for the lookback period, and then generates a moving average forecast of cloud spend for the specified months.

Predicting what you may spend on cloud is a challenging task given the variable nature of cloud consumption and the effects of optimization activities such as reservations and rightsizing. Our Cloud Spend Forecast policies provide a number of ways to gain some insight into what your future spend may look like.

The following policies can be applied:

This policy uses the Straight-Line method using the Simple model, which uses a more basic calculation than the Linear Regression model to forecast your spend.

You can choose to forecast at the Billing Center or entire Organization level, specify how many months of historical data should be considered, and specify how many months should be forecasted. In addition, you can choose to breakdown forecasted costs by the following dimensions: category, region, service, and vendor account (for example, AWS account, Azure subscription, and so on).

Emails a list of cost recommendations pulled from the Flexera Optimization dashboard.

Finds Google Cloud Platform committed use discount recommendations and reports when it finds them.

Reports on any idle Cloud SQL instances identified by the Google Recommender service. You can then choose to stop or delete the Cloud SQL instance if desired. Optionally, you can filter results by label, project ID/name, or region.

Finds idle IP addresses and reports when it finds them. You can then delete the idle IP addresses.

Checks Google Cloud Platform storage objects for the last updated time and moves the object to nearline or coldline. To delete the object, enable the delete action as mentioned in README.md.

Finds Google Recommendations and reports when it finds them.

Finds underutilized and idle Google VM instances and downsizes, stops, or deletes them after approval.

Recommends Kubernetes cluster configuration for performance and cost optimization.

Analyzes all account usage and recommends consolidation or deletion.

Analyzes bills for new service usage and sends email notifications.

Generates a reserved instances report by billing center.

Allows you to configure scheduled reports that will provide summaries of cloud cost.

Utilizes Turbonomic endpoint to provide Azure VM allocation recommendations for Reserved Instance coverage. From these recommendations, we provide monthly savings estimates based on Turbonomic per hour costs.

Uses the Turbonomic Actions API to provide purchase recommendations for AWS reserved instances. Details on these endpoints can be found in the readme file of the policy.

Uses the Turbonomic Actions and Business Units API endpoints to provide recommendations for deleting unattached AWS volumes. Details on these endpoints can be found in the readme file of the policy.

Uses the Turbonomic Actions and Business Units API endpoints to provide recommendations for deleting unattached Google Cloud Platform volumes. Details on these endpoints can be found in the readme file of the policy.

Uses the Turbonomic Actions and Business Units API endpoints to provide recommendations for rightsizing Azure databases and database servers. Details on these endpoints can be found in the readme file of the policy.

Uses the Turbonomic Actions and Business Units API endpoints to provide recommendations for rightsizing Azure virtual machines. Details on these endpoints can be found in the readme file of the policy.

Uses the Turbonomic Actions and Business Units API endpoints to provide recommendations for rightsizing AWS virtual volumes. Details on these endpoints can be found in the readme file of the policy.