Remediate 4-aws-finops-unattached-volume-vol-0e620fc9c3b6d55db (run 28592024706.1)

remediations/proposed/28592024706-1/4-aws-finops-unattached-volume-vol-0e620fc9c3b6d55db/finding.json

@@ -0,0 +1,32 @@
+{
+  "run_id": "28592024706",
+  "target": "finops-aws",
+  "provider": "aws",
+  "check_id": "aws-finops-unattached-volume",
+  "check_file": "finops-aws/unattached-volumes.yaml",
+  "check_name": "Unattached EBS volumes",
+  "query": "SELECT volumeId, size, status, AvailabilityZone, volumeType, createTime\nFROM aws.ec2_native.volumes\nWHERE region = 'ap-southeast-2'",
+  "severity": "LOW",
+  "category": "waste",
+  "kind": null,
+  "region": "ap-southeast-2",
+  "suggested_remediation": {
+    "type": "delete",
+    "tool": "stackql",
+    "preflight_query": "SELECT volumeId FROM aws.ec2_native.volumes WHERE region = 'ap-southeast-2' AND volumeId = 'vol-0e620fc9c3b6d55db' AND status = 'available'\n",
+    "sql_query": "DELETE FROM aws.ec2.volumes WHERE region = 'ap-southeast-2' AND VolumeId = 'vol-0e620fc9c3b6d55db'\n",
+    "command": null,
+    "description": "Delete the unattached EBS volume (snapshot first if its data may be needed)."
+  },
+  "fields": {
+    "AvailabilityZone": "null",
+    "createTime": "2026-01-09T03:01:34.970Z",
+    "size": "1",
+    "status": "available",
+    "volumeId": "vol-0e620fc9c3b6d55db",
+    "volumeType": "gp2",
+    "region": "ap-southeast-2",
+    "category": "waste",
+    "estimated_monthly_usd": 0.1
+  }
+}

remediations/proposed/28592024706-1/4-aws-finops-unattached-volume-vol-0e620fc9c3b6d55db/preflight.sql

@@ -0,0 +1 @@
+SELECT volumeId FROM aws.ec2_native.volumes WHERE region = 'ap-southeast-2' AND volumeId = 'vol-0e620fc9c3b6d55db' AND status = 'available'

remediations/proposed/28592024706-1/4-aws-finops-unattached-volume-vol-0e620fc9c3b6d55db/rationale.md

@@ -0,0 +1,7 @@
+(a) This removes the unattached EBS volume `vol-0e620fc9c3b6d55db` (1 GiB, gp2) in region `ap-southeast-2` via a `DELETE FROM aws.ec2.volumes`. The volume is reported as `status = available`, i.e. not attached to any instance.
+
+(b) Confidence: high. The preflight query re-asserts both the exact volume id and `status = 'available'` immediately before deletion, so the delete only proceeds if the volume is still genuinely unattached.
+
+(c) Captain's call: the volume carries no visible Name tag or other metadata, so a deterministic check cannot tell whether its data is still needed. It is only 1 GiB and was created on 2026-01-09T03:01:34.970Z — all volumes in this batch were created within minutes of each other on 2026-01-09, which suggests an automated or test provisioning run; confirm it is not a template/scratch disk that will be re-attached before deleting. Deletion is irreversible, so snapshot first if in doubt.
+
+(d) Estimated monthly saving: $0.10 USD.

remediations/proposed/28592024706-1/4-aws-finops-unattached-volume-vol-0e620fc9c3b6d55db/remediation.sql

@@ -0,0 +1 @@
+DELETE FROM aws.ec2.volumes WHERE region = 'ap-southeast-2' AND VolumeId = 'vol-0e620fc9c3b6d55db'