Mods
AWS

Policy: AWS > Batch > Compute Environment > Active > Age

The age after which the AWS Batch compute environment is no longer considered active. If a create time is unavailable, the time Guardrails discovered the resource is used.

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 > Batch > Compute Environment > 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 age > 1 day
    
  • Force inactive if age > 3 days
    
  • Force inactive if age > 7 days
    
  • Force inactive if age > 14 days
    
  • Force inactive if age > 30 days
    
  • Force inactive if age > 60 days
    
  • Force inactive if age > 90 days
    
  • Force inactive if age > 180 days
    
  • Force inactive if age > 365 days
    
Examples [YAML]
  • Force inactive if age > 90 days
    

Category

In Your Workspace

Developers