CASE 80 · PLENUM · 2024
"What do we own and where?", answered by a search box.
A healthcare platform had grown to 40 accounts and nobody could answer simple inventory questions ("how many Lambdas across the org," "which accounts have RDS in eu-west-1") without spending half a day on aggregated CLI scripts. We deployed AWS Resource Explorer with a cross-account aggregator index.
Healthcare platform
LANDING ZONE
2024
RESULTS
What changed, by the numbers.
INVENTORY-QUESTION TIME
< 10s
ACCOUNTS INDEXED
40
STALENESS
< 30m
OPS-LED INVENTORY SCRIPTS
RETIRED
HOW IT WENT
Inventory scripts had calcified into a small library nobody trusted entirely. Each script took an account list and an SSO profile and ran sequentially. A "how many Lambdas do we have" question took most of a morning, and the answer came with footnotes about which accounts had failed authentication.
Resource Explorer with a cross-account aggregator solved the problem at the AWS layer. The aggregator index landed in the security account; team-specific views surfaced through QuickSight dashboards. Tag policies (already in place) gave the search box useful filters.
Engineers who used to ask "can someone run the script" now type into a search box. Inventory questions are answered in under ten seconds. The legacy scripts moved to a "retired" folder; two were preserved for genuine edge cases Resource Explorer doesn’t cover (Step Functions execution history, for instance).
RELATED · SAME DOMAIN
Other engagements in this space.
READY WHEN YOU ARE
Let's get your AWS bill (and architecture) in order.
The discovery call is free. You walk away with at least one concrete idea — even if we never work together.