superseded_instance

Superseded Instances Policy Template

Deprecated

This policy is no longer being updated. Please use the version of this policy specific to the cloud environment you need recommendations for.

• AWS Superseded EC2 Instances
• Azure Superseded Compute Instances

What It Does

The Superseded Instances Policy Template is used to monitor an account a generate a list of superseded instances. This policy supports AWS, Azure, and AzureCSP. It also allows use of AMD, and Burstable types as replacement. There are fundamental differences between this and Optima Superseded Instances recommendations.

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

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

Usage

This policy used Optima data to get a list of instances used in the month and their possible new types, as well it uses data in Policies Data to determine if an instance type has been superseded. It will then list all the instances that have been superseded and their types. The Monthly Estimated Cost is an estimated cost for the instances with the current configuration, you will save a portion of that by moving to the instance type, the new instance types should be more performant as well. If the New Instance Type value in the incident report is "Unavailable", the current instance type does not currently exist in our Instance Type mapping. Please raise an issue for the mapping to be updated with the current instance type.

Input Parameters

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

• Email addresses - A list of email addresses to notify
• Billing Center Name - List of Billing Center Names to check
• Minimum Savings Threshold - Specify the minimum monthly savings value required for a recommendation to be issued, on a per resource basis. Note: this setting applies to all recommendations. Example: 1.00
• Minimum Instance Savings Threshold - The recommended action for some recommendations may require an instance relaunch. Specify the minimum monthly savings value required for a recommendation of this nature to be issued, on a per instance basis. Note: this setting applies to multiple recommendations. Example: 100.00
• Instance Type Category - Instance Type Category to pick from.
  1. regular: AWS/Azure - Matches Optima Recommendation data
  2. next_gen: AWS - Latest generation upgrade
  3. burstable: AWS - If an instance can be replaced by a burstable type this will be recommended
  4. amd: AWS - next_gen + a series to allow you to use amd types for even more savings.

Supported Clouds

• AWS
• Azure

Cost

This policy template does not incur any cloud costs.