Mods
AWS

Policy: AWS > EC2 > Key Pair > Active > Budget

The impact of the budget state on the active control. This policy allows you to force keyPairs to inactive based on the current budget state, as reflected in AWS > Account > Budget > State

The Active control determines whether the resource is in active use, and if not, has the ability to delete / cleanup the resource. When running an automated compliance environment, it's common to end up with a wide range of alarms that are difficult and time consuming to clear. The Active control brings automated, well-defined control to this process.

The Active control checks the status of all defined Active policies for the resource (AWS > EC2 > Key Pair > Active > *), raises an alarm, and takes the defined enforcement action. Each Active sub-policy can calculate a status of active, inactive or skipped. Generally, if the resource appears to be Active for any reason it will be considered Active. Note the contrast with Approved, where if the resource appears to be Unapproved for any reason it will be considered Unapproved.

See Active for more information.

Resource Types

This policy targets the following resource types:

Primary Policy

This policy is used with the following primary policy:

Controls

Policy Specification

Schema Type
string
Default
Skip
Valid Values [YAML]
  • Skip
    
  • Force inactive if Budget > State is Over or higher
    
  • Force inactive if Budget > State is Critical or higher
    
  • Force inactive if Budget > State is Shutdown
    
Examples [YAML]
  • Skip
    

Category

In Your Workspace

Developers