Skip to content

Global Professional Services Organization Professional services

Leaving a managed hosting provider for a governed AWS landing zone

Migration from a managed hosting provider to AWS, built on a multi-account landing zone with security, monitoring and disaster recovery designed in.

Representative experience of the VBR engineering team. The organization is not named, and internal details are omitted.

Challenge

  • Core systems ran on managed hosting that limited control over security, scaling and cost.
  • The organization needed a cloud foundation that could support future growth with clear governance.
  • Disaster recovery capability needed to be designed, not inherited from the hosting contract.

Business context

The organization serves a global membership and needed its platforms to be available, secure and auditable while it moved off its hosting provider.

Architecture

Hosting to AWS migrationinspection point

Simplified view. Internal names, addresses and configuration are omitted.

Solution

  • Assessed the hosted estate and planned the migration by workload.
  • Built an AWS landing zone with AWS Organizations, IAM guardrails and centralized logging.
  • Migrated compute to EC2 and ECS, and data to RDS, FSx and S3.
  • Enabled GuardDuty, Security Hub, CloudTrail and CloudWatch across accounts.
  • Defined infrastructure in Terraform and CloudFormation, with disaster recovery and cost governance built in.

Technology

  • AWS Organizations
  • EC2
  • ECS
  • S3
  • RDS
  • FSx
  • IAM
  • GuardDuty
  • Security Hub
  • CloudTrail
  • CloudWatch
  • Terraform
  • CloudFormation

Engineering approach

  1. Step 1

    Assess

    Inventoried servers, databases, file shares and dependencies on the hosted platform.

  2. Step 2

    Land

    Deployed the landing zone and security baseline before migrating workloads.

  3. Step 3

    Migrate

    Moved workloads in planned sequences with validation at each step.

  4. Step 4

    Optimize

    Tuned sizing and established cost visibility after cutover.

Security

  • Multi-account isolation with AWS Organizations
  • Threat detection with GuardDuty
  • Posture management with Security Hub
  • Audit trail with CloudTrail
  • Least-privilege IAM

Outcomes

  • Exit from managed hosting onto infrastructure the organization controls
  • A governed multi-account foundation for future workloads
  • Continuous security monitoring and audit logging across accounts
  • Designed disaster recovery and clearer cost visibility

Discuss a similar transformation

We'll talk through your environment and how we approached comparable work.