Rambunct gave Checkcomm a spend review of its multi-account Amazon Web Services (AWS) organisation, by account and service with a forecast and recommendations, and a security review of the accounts in scope with a prioritised roadmap. Both are assessments with recommendations.
The challenge
Checkcomm, a UK telecommunications company, hosts its PBX telephony and voice services on Amazon Web Services (AWS) in one multi-account AWS organisation. It wanted to formalise the security posture of its accounts and to understand its AWS spend in detail. Its pain points were:
- Monthly spend rose by about 149% in a year
- Month-to-date spend was already above its single monthly budget
- None of its cost allocation tags was active, so spend could not be split by tag
- Everything ran on demand
The solution
Rambunct’s work for Checkcomm’s Amazon Web Services (AWS) organisation was assessment with recommendations, made through view-only access to some of its accounts. Rambunct worked with Checkcomm on calls.
Spend review:
- Showed the spend by account and service with AWS Cost Explorer and forecast the year
- Set out recommendations, most with an estimated monthly saving or avoided cost
- Advised right-sizing before any commitment
Security review:
- Based on a Prowler scan of the accounts it could read
- Set out a prioritised roadmap of actions, each with what to do and when
Guardrail:
- Designed and configured an Amazon Bedrock guardrail for the customer’s voice-analysis function; no result of it is claimed
Architecture
The assessment read Checkcomm’s Amazon Web Services (AWS) organisation through a view-only permission set on some of its accounts, with AWS Cost Explorer in the payer account for spend and forecast and the Prowler scanner for the security checks.
AWS services:
AWS Organizations, AWS Cost Explorer
Results
- Gave Checkcomm its spend by account and service, shown in charts
- Set out recommendations, most with an estimated monthly saving or avoided cost, with right-sizing first
- Set out a prioritised security roadmap, with the most urgent actions scheduled for its first two weeks
No customer action is recorded, so no saving or fixed finding is claimed.






