Attack in progressA leaked CI key of ‹ci-deploy-bot› is being used to break in: 6 accounts and machines created.Open the case
Install
What this console can check of its own setup from inside the cluster it runs in: 7 of 7 in place. Every other cluster in your accounts is on Clusters.
Health: whether Firekeeper is watchingFootprint: what Firekeeper runs in your accounts and what it costs
| Check | State | What the console found |
|---|---|---|
| Sign-in | in place | You signed in through Firekeeper's AWS sign-in (load balancer firekeeper-firekeeper-dev). Sign out |
| Your role | in place | You are a keeper: a person whose passkey approves changes. |
| Firekeeper's record | in place | The console can read Firekeeper's record. |
| The last run | in place | The last run finished at 2026-09-12 06:04 UTC and pushed. |
| Your passkeys | in place | You can sign decisions with 1 passkey. |
| Who can sign | in place | 2 keepers can sign decisions. |
| The schedule | in place | Firekeeper scans every day (UTC). The next run starts at 2026-09-13 06:00 UTC. |