CASE 83 · ONYX · 2024
A self-service catalog the central team isn’t a bottleneck for.
A manufacturing company’s cloud team was running infrastructure as a ticket queue. Every new database, every new VPC, every new IAM role was a ticket. We launched AWS Service Catalog with curated portfolios and let the engineering teams self-serve from approved patterns.
Manufacturing
LANDING ZONE
2024
RESULTS
What changed, by the numbers.
TICKET QUEUE
−81%
PORTFOLIOS
4
PRODUCTS
23
PROVISIONING TIME
< 20m
HOW IT WENT
The cloud team had become a bottleneck by accident. They’d been the gatekeepers for "doing it right" — but the queue had outgrown them. Provisioning a development database took five days because the request was buried behind security reviews of other requests.
Service Catalog let them codify "doing it right" into CloudFormation templates with parameter-controlled variations. The Data portfolio held RDS, Aurora, DynamoDB, Redshift templates. The Network portfolio held VPC, subnet, security group patterns. Identity Center mapped permissions per portfolio.
Provisioning time fell from days to minutes for the 23 patterns covered. The cloud team’s ticket queue dropped 81% — they kept the 19% that genuinely required custom thinking, which was the work they’d been trying to do all along.
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.