De-risking a live fraud platform before it moves clouds

A SaaS B2B business working with Cloud Combinator on AWS. The client is anonymised at their request.

The challenge had three focus areas, each a reason the migration could not simply be attempted directly.

Because the whole platform is already built as infrastructure as code across four repositories, Cloud Combinator could build the assessment from what actually runs rather than from memory. The work runs end to end as a sequence: agree the access model, inventory both workloads from the IaC, give every component a 7Rs disposition and a named AWS target, assemble the target architecture in eu-west-1 with an us-east-1 replica, build the cost model in the AWS Pricing Calculator against current run cost, score readiness against the AWS Migration Readiness Assessment and Well-Architected pillars, then sequence the migration into waves with rollback points and deliver a clear go or no-go.

The assessment is scoped to hand the client a plan it can act on with confidence: both workloads fully inventoried, every component mapped to a confirmed AWS target with zero unmapped items at sign-off, a costed business case, a readiness score, and a safe wave sequence. The bar for done is that the plan is validated, costed, and safe to execute.

• Complete coverage — Both the platform and ML Core workloads are inventoried from the four IaC repositories, with each component given a 7Rs disposition and mapped to a confirmed AWS service.
• A costed business case — A total cost of ownership model is built line for line in the AWS Pricing Calculator, with an indicative annual AWS run cost of around 565,000 USD for the core workload as currently estimated (projected, and to be reconfirmed against the full target).
• A safe migration plan — A wave sequence with rollback points is produced for the real-time path, sized so the live fraud stream carries no data-loss tolerance during cutover.
• Readiness, measured not asserted — The target is scored against the AWS Migration Readiness Assessment framework and the Well-Architected pillars, with high risk items documented and their fixes named.
• Handover — The assessment report, target architecture, TCO model, and migration plan are delivered to the client as the foundation for the platform phase.

With the plan validated, the client moves into the platform and the migration itself as separate phases, reusing the assessment artefacts and the infrastructure as code so each later phase is cheaper per unit of scope. The outcome is a platform no longer split across two clouds, but consolidated onto AWS on a validated, funded, and auditable path.