Everything I could decide myself is decided. What's left needs
you. Each one carries the recommendation of the session that raised it — if you
agree, pick it and press Done. A model's opinion, where there is one, appears on the card
as a receipt line; cards with no receipt were never put to a model. "I'm not sure" is a real answer and becomes work for me.
You don't need to open the session — pressing Done sends your answer back and it picks up.
1AWS Config is still recording every throwaway CI runner RunsOn creates (35,107 EC2Fleet + instances/ENIs/volumes). Overnight override put 3 of 4 types on daily recording, but daily items cost 4x each and EC2Fleet (the biggest) was left on continuous. How do we stop the remaining Config bleed?
In plain terms. Config is a service that writes a note every time any AWS resource changes, at about a third of a cent per note. Our new CI runners create and destroy thousands of resources a day, so it wrote ~120,000 notes a day (~$375). Should we tell Config to stop taking notes on those short-lived CI machines?
The session raising this recommends: Exclude the 4 ephemeral EC2 types from Config recording Every EC2 resource in this account is a runs-on CI runner that lives ~10 min; Security Hub only loses checks on those. Config keeps recording IAM, Lambda, DDB, S3 and the rest. Daily mode still bills $0.012 per item per resource, and EC2Fleet alone is 57% of tracked resources. Tried first, unsuccessfully: Tried: the daily-override path (applied 2026-09-17 04:51Z) — incomplete and 4x per-item; measured Sep 16 still at 52,200 items (~$157). Not tried: exclusion, because changing the recorder is a prod-infra change that stays a human call.