1. Kion Success Center
  2. Settings
  3. Application Settings

Savings Opportunities Settings

Follow

Last updated

Savings Opportunities Settings

Settings > System Settings > Application Settings > Savings Opportunities

Configure the savings opportunity settings for your whole organization, including turning savings opportunity checks on and off.

Since these configurations change the user interface for all users in your organization, these settings can only be changed by users with the Global Manage Kion System Settings permission.

Allow users to stop or terminate resources from within Kion

Allow users with the appropriate permissions to temporarily stop or permanently terminate a resource from within Kion. This makes it easy to decommission a resource that is not being utilized. Use this option with caution. Terminating the wrong resources can disrupt services in your production environment. For more information about setting permissions for this, see the Address section of the Permission Levels article.

POST Token Life

Customize the POST token life for savings opportunities webhooks. This sets the amount of time allowed to execute your Cloud Custodian opportunity checks policies.

If you have opportunity checks that take longer than an hour to run, a token set to one hour would expire before the scan completes, and the results wouldn't successfully POST within the API. To ensure these long-running scans are successful, you can increase the POST token life to a maximum value of four hours.

The default value for the savings opportunity token life is one hour, which is sufficient for most setups and follows best practices by limiting the token life.

Opportunity Checks

You will only see savings opportunity checks for cloud providers you have enabled. To enable cloud providers, see Cloud Provider Settings.

Once an opportunity check is enabled, Kion scans your cloud environments every 12 hours for resources that meet that opportunity check's criteria.

For more information about rightsizing, decommissioning, and savings opportunity checks, see What is a Savings Opportunity? 

Configurable Opportunities

AWS

  • EBS Volumes - Gp2 to Gp3
  • EBS Volumes - Io1 and Io2 to Gp3
  • EC2 Instances With Average CPU Utilization 10% or Les
  • EC2 Instances With Average CPU Utilization Between 10% and 20%
  • EC2 Instances at least 7 days old with average CPU utilization between 10% and 20%
  • EC2 Instances With Average CPU Utilization Between 20% and 30%
  • EC2 Instances at least 7 days old with average CPU utilization between 20% and 30%
  • EC2 Instances With Average CPU Utilization Between 30% and 40%
  • EC2 Instances at least 7 days old with average CPU utilization between 30% and 40%
  • RDS Instances Utilizing 10% CPU or Less in 14 Days
  • RDS Instances With Max CPU Utilization Between 10% and 20%
  • RDS Instances With Max CPU Utilization Between 20% and 30%
  • RDS Instances With Max CPU Utilization Between 30% and 40
  • RDS Instances With Max CPU Utilization Between 40% and 50%
  • RDS Previous Generation
  • Amazon MQ Brokers With No Established Connections in 7 Days
  • Application Load Balancers With Empty Target Groups
  • Application Load Balancers With No Connections
  • Classic Load Balancers With No Connections
  • Classic Load Balancers With No Instances
  • EBS Snapshots 30 to 60 Days Old
  • EBS Snapshots 60 Days Old or Older
  • EBS Unattached Older Than 14 Days
  • EFS Volumes With 0% IO Limit Used in 14 Days
  • Network Load Balancers With Empty Target Groups
  • RDS Cluster Snapshots 60 Days or Older
  • RDS Cluster Snapshots Between 30 and 60 Days Old
  • RDS Databases With No Connections in 14 Days
  • RDS Snapshots 60 Days Old or Older
  • RDS Snapshots Between 30 and 60 Days Old
  • Redshift Databases With No Connections in 14 Days
  • Redshift Snapshots 60 Days Old or Older
  • Redshift Snapshots Between 30 and 60 Days Old
  • Unattached Elastic IPs
  • Workspaces That Have Never Been Connected To
  • Workspaces With No User Connections in 30 Days

Azure

  • Azure VMs With Average CPU Utilization 10% or Less
  • Azure VMs With Average CPU Utilization Between 10% and 20%
  • Azure VMs With Average CPU Utilization Between 20% and 30%
  • Azure VMs With Average CPU Utilization Between 30% and 40%
  • Azure VMs With Average CPU Utilization Between 40% and 50%
  • Azure Load Balancers With 0 Transmitted Packets in 14 Days
  • Azure VM Disks That Are Not Managed by a VM
  • SQL Server Databases With No Connections in 14 Days
  • PostgreSQL Servers With No Connections in 14 Days