Skip to content
Dependable · Cloud Migration & Cost Optimization (Azure, AWS, M365)

A cloud environment with no disaster-recovery plan was rebuilt from code in about 40 minutes

A global financial market-data provider. Outcome verified

about 40 minutes

The problem

A global financial market-data provider ran its flagship product on a large cloud footprint but had no cold disaster-recovery option. If the production cloud account were seriously damaged, there was no tested way to rebuild it. The environment had grown by hand for years, with dozens of interdependent resources and no record of what a rebuild would require.

Why it mattered

A destructive attack or an administrative error could take a revenue-producing product offline indefinitely, with no rebuild path and no way to estimate recovery time.

What we did

Rather than document the environment by hand, Vizius extracted the live production resources into infrastructure templates, deployed them into a separate backup account and restored the database from a point-in-time snapshot, proving the approach end to end. It then recorded the manual steps still standing between proof of concept and production-ready failover.

What changed

The proof-of-concept template recreated 74 cloud resources, with working service functionality, in a backup account in roughly 40 minutes. The deliverable also listed the remaining automation work needed to make it a viable ongoing failover option.

  • Financial services
  • Midsize company

Sound familiar?

  • If our AWS account were deleted tomorrow, I don't know how we'd rebuild it
  • We've never tried to stand the whole thing back up
  • Our cloud was built by hand and nobody has the full picture
How we did it

Cloud Migration & Cost Optimization (Azure, AWS, M365)

"Can we move or merge this without breaking our apps?"

We build Azure and AWS from code so it can be rebuilt fast, migrate tenants and mail after acquisitions, and cut storage and compute spend.