Cloud Transformation

Business-Critical Windows Systems Rehosted on AWS

Windows and .NET systems moved to EC2 across two Availability Zones, with SQL Server Always On between them.

Web and application servers run in Auto Scaling groups behind a load balancer, one copy per zone. Cache, search and queue clusters and SQL Server Always On span both zones; Active Directory moves with them. Offices connect over VPN; files go to S3.

HTTPSsynchronous commitclusterVPNsign-in, adminOn premisesAWS CloudVPC · one Region, two Availability ZonesPublic subnetsPrivate subnets · web, appPrivate subnets · data, directoryAvailability Zone AAvailability Zone BUserspublic, HTTPSOfficesstaff, adminsElastic LoadBalancingApplication LBWeb serversAuto Scaling groupApp serversAuto Scaling groupSQL ServerAlways On primaryCache, search, queueclustered on EC2Web serversAuto Scaling groupApp serversAuto Scaling groupSQL ServerAlways On secondaryCache, search, queueclustered on EC2AWS Site-to-Site VPNActive Directorya domain controller per zoneAmazon S3files, documentsAmazon CloudWatchalarmsAWS BackupAMIs, EBS snapshots

Point at a component to light its links; select it for what it does here and the practice that makes it right on AWS.

When to use it

  • Windows, .NET and SQL Server systems that must move before they can modernise
  • Systems where an outage stops the business, so one zone is not enough
  • A data-centre exit with offices that keep working through the move

How NGT delivers it

Built from code, reviewed at a gate by an NGT architect, and handed over with runbooks your team can run.

Cloud Transformation