Policy Packs

guardrails-samples

This practice helps avoid unnecessary costs associated with unattached volumes, reduces the risk of data exposure, and ensures that all storage resources are actively managed and utilized.

Enforce AWS EBS Volumes Are Attached to EC2 Instances

main

aws_ec2_volume_approved

Determine the action to take when an AWS EC2 volume is not approved based on `AWS &gt; EC2 &gt; Volume &gt; Approved &gt; *` policies.&#92;n&#92;nThe Approved control checks the status of the defined Approved sub-policies for the resource. If the resource is not approved according to any of these policies, this control raises an alarm and takes the defined enforcement action.&#92;n&#92;nFor any enforcement actions that specify `if new`, e.g., `Enforce: Delete unapproved if new`, this control will only take the enforcement actions for resources created within the last 60 minutes.&#92;n&#92;nSee [Approved](https://turbot.com/guardrails/docs/concepts/guardrails/approved) for more information.&#92;n

volumeApproved

AWS > EC2 > Volume > Approved

aws_ec2_volume_approved_custom

Determine whether the AWS EC2 volume is allowed to exist.&#92;nThis policy will be evaluated by the Approved control. If an AWS EC2 volume is not approved, it will be subject to the action specified in the `AWS &gt; EC2 &gt; Volume &gt; Approved` policy.&#92;nSee [Approved](https://turbot.com/guardrails/docs/concepts/guardrails/approved) for more information.&#92;n&#92;n**Note**: The policy value must be a string with a value of `Approved`, `Not approved` or `Skip`, or in the form of YAML objects. The object(s) must contain the key `result` with its value as `Approved` or `Not approved`. A custom title and message can also be added using the keys `title` and `message` respectively.&#92;n

Developers