CloudGoA production system had grown harder to understand.
Berner’s connected IoT platform was stable, but its AWS environment had become more complex as it scaled. Device authentication and API policies were distributed, some serverless components needed upgrades, and cloud costs did not clearly track expected usage. Existing dashboards and billing views showed pieces of the problem. The team needed a view of how the pieces connected.
The context behind the decision.
CloudGo used read-only access to assess the existing AWS environment. The analysis looked across device authentication, API access, serverless dependencies, and usage patterns to understand the platform as a connected system.
What the connected picture revealed.
A dependency holding back modernization
A shared component was blocking runtime upgrades across much of the serverless environment.
Access controls that needed consistency
Device credentials and API permissions were broader and less consistent than appropriate for the platform’s scale.
A cost driver hidden in the relationships
A specific usage pattern accounted for a meaningful share of spend, but was difficult to identify from standard billing views alone.
A plan the team could work from.
The team received a phased roadmap within days, with a sequence for strengthening access controls, modernizing shared serverless components, and introducing lightweight cost and configuration governance. The proposed approach organized the changes incrementally, with production continuity in mind.
- Prioritized security and access-control recommendations
- A targeted plan for shared runtime modernization
- Cost and configuration governance guidance
- An incremental remediation sequence
Read the original case study · Download the full PDF