All apps

AWS Console Diagnostics

What is dead, exposed and broken in an AWS account

Three numbers on sign-in, every finding with the evidence behind it, and how old the answer is.

An engineering lead signs in and sees how many things in the account are dead, exposed and broken, read live from a graph of the estate. Every finding shows the observations it rests on, including the admission that nothing was measured. Triage sticks: acknowledge, dismiss with a reason, or snooze until a date, and the decision survives the next scan.

Open the live app Build your own
The Console Diagnostics sign-in: a black panel with a faint estate graph drawn across it, and a sign-in card on the right
The front door, with the estate graph it is about drawn faintly behind it.
The Console Diagnostics sign-in on a phone
The same screen on a phone.

Built for named people, not job titles.

Before anything was built, the people who would use it were written down by name. Each one gets a real account, and every screen is clicked through as each of them before it ships.

  • Nadia

    VP Engineering

    Wants the three numbers and whether they moved since last month.

  • Omar

    Staff engineer

    Wants the observation behind a finding before he believes it.

One milestone at a time.

This is the plan the app was built from. Each milestone is written in plain words, together with the check that proves it works.

4 milestones, 4 built

  1. 1

    The three sections

    built

    Sign in and see how many things are dead, exposed and broken — read live from the graph.

    How we check it: The estate is summarised in three numbers

    1. Given the graph holds resources that are dead, exposed and broken
    2. When 'lead' opens the app
    3. Then she sees a count for dead, a count for exposed and a count for broken
    4. And opening the dead count lists the dead findings
    5. And each finding shows the category it is in and how confident the tool is
  2. 2

    A finding and how we know

    built

    Every finding shows the observations behind it, including that nothing was measured.

    How we check it: A verdict comes with its reasons

    1. Given a dead finding with a measured size and a measured usage count
    2. When 'lead' opens that finding
    3. Then she sees the size and the usage count in units she recognises
    4. And each observation says whether it supports the finding or contradicts it
  3. 3

    Triage a finding

    built

    Acknowledge, dismiss with a reason, or snooze until a date — and it sticks across scans.

    How we check it: A dismissal needs a reason and then it sticks

    1. Given a finding 'engineer' believes is fine
    2. When he dismisses it with a reason
    3. Then it no longer appears in the default list
    4. And it appears when dismissed findings are shown, with his reason and his name
  4. 4

    How old is this answer

    built

    The age of the graph, and its reachability, as permanent furniture on every screen.

    How we check it: The age of the data is always on screen

    1. Given the graph was last collected some days ago
    2. When 'lead' opens the app
    3. Then she sees how long ago it was collected, without asking for it
Body KnowledgeClick a muscle, read what it means. Pick a feeling, watch the body light up.Next in the showcase

Your business, on its own app.

Pikku Studio is free and runs on your computer. Start from the spreadsheets, folders and chats you already have.

Download Pikku StudioSee the other apps