Detached Volumes Detected
Overview
The Detached Volumes Detected trigger allows you to trigger a rule's execution when a volume is detected as being detached from an instance. It is particularly useful for cleaning up resources that have been left behind after an instance has been terminated.
Use of this trigger in a rule
The Detached Volumes Detected trigger will usually be used in a rule with a Delete Detached Volumes action to clean up detached volumes. However, it is possible to pair it with any action.
If paired with a Delete Detached Volumes action, and the "number of days" specified in the action configuration is higher than the "number of days" specified in the trigger configuration, the action the volumes will not be deleted.
Configuration
Number of Days Detached
The trigger will be activated when a volume has been detached for the number of days specified in this field.
The number of days that a Volume has been detached for is tracked by GorillaStack, therefore this metric does not work retrospectively for Volumes that were already detached when your account was linked. For these Volumes, we consider the account linked date as day 0.