01

Five clouds, one way of working

Most work runs on AWS, Azure and Google Cloud; the same method carries to Huawei Cloud and Alibaba Cloud.

Partners of all five

FPT Software is a partner of AWS, Microsoft, Google Cloud, Huawei Cloud and Alibaba Cloud. Where a partner programme allows, it can help fund a proof of concept.

02

One design, drawn for each cloud

Use the switch: the same web application on AWS, Azure and Google Cloud, each with its own services.

Web Application on Managed Services
cache missessyncimagesInternetAWS CloudAround every tierEdge locations · globalPublic subnetsPrivate subnets · appPrivate subnets · dataAvailability Zone AAvailability Zone BManaged services in the regionUsersAmazon Route 53AWS WAFon CloudFrontAmazon CloudFrontApplication LoadBalancerin both zonesAmazon EKSnodes in zone AAmazon EKSnodes in zone BAmazon Aurora / RDSfor PostgreSQLprimaryAmazon Aurora / RDSfor PostgreSQLstandbyAmazon ElastiCacheprimaryAmazon ElastiCachereplicaAmazon ECRAmazon MQAmazon S3Amazon EFS or FSxEventBridgeSchedulerAWS IAMEKS Pod IdentityAWS Secrets ManagerAmazon CloudWatchAWS CloudTrailAWS Backup

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

Point at a component to see what it does; select it for the best practice.Open the architecture
03

The same job on AWS, Azure and Google Cloud

One method, mapped to each provider's framework and tools, so your teams recognise what they get.

AWSAWS Well-Architected · Migration Acceleration Program phases
  • Multi-account landing zone: Organizations and Control Tower, in Terraform or CloudFormation
  • Discovery and TCO: Application Discovery Service, Migration Hub, Migration Evaluator
  • Servers by Application Migration Service; databases by DMS and SCT
  • Containers on EKS or ECS Fargate; CI/CD on CodePipeline, GitLab or Jenkins
AWS Control TowerAWS OrganizationsAWS Application Migration ServiceAWS DMSAmazon EKSAWS FargateAmazon CloudWatch
Microsoft AzureMicrosoft Cloud Adoption Framework · Azure Well-Architected
  • One Microsoft Entra tenant: a connectivity subscription with the hub, application subscriptions as spokes
  • Azure Migrate, Data Migration Assistant, Azure Database Migration Service and SSMA
  • Private AKS behind hub-and-spoke networking, Azure Bastion and Private Link
  • Approval-gated Terraform in Azure DevOps, with Azure Policy and Cost Management
Azure MigrateAzure Database Migration ServiceAKSAzure FirewallAzure PolicyAzure MonitorCost Management
Google CloudGoogle Cloud Architecture Framework · adoption framework
  • Assessment, planning, a pilot as MVP, then launch, with a gate after each step
  • Infrastructure provisioned with Terraform through pipelines
  • Migrate to Virtual Machines and Database Migration Service; Cloud Monitoring and Logging from day one
  • GKE with secure CI/CD; DR across regions; budget alerts, rightsizing, committed-use discounts
Migrate to Virtual MachinesDatabase Migration ServiceGKECloud MonitoringCloud LoggingCloud Storage
04

Moving between clouds, regions and data centres

Multi-cloud is rarely everything everywhere. These are the moves customers actually ask for.

  • Cloud to cloudOne provider to another, with a reference DevSecOps pipeline so delivery keeps going.
  • Region to regionRehosted into an improved landing zone in the new region, then the old one decommissioned.
  • Hybrid, seen as oneVPN, Direct Connect or ExpressRoute, hybrid DNS and directory; on premises in the same monitoring.
  • Portable and regulatedKubernetes and Terraform per cloud; reusable templates for each provider.
Hybrid Network and Identity
sign in onceidentity sourceforest trustcloud nameson-premises namesspokesdomain joinOn premisesAWS CloudIdentityShared services accountNetwork accountWorkloads OUProduction accountVPC · spokeNon-production accountVPC · spokeUsers and officesAD domaincontrollersDNS serversData centreservers still to moveAWS Direct Connectprimary pathAWS Site-to-Site VPNbackup pathIAM Identity CenterAWS ManagedMicrosoft ADRoute 53 ResolverAWS Transit GatewayAWS Network FirewallAmazon EC2domain-joinedAmazon RDS for SQLServerAmazon EC2pilot serversAmazon RDS for SQLServer

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

Point at a component to see what it does; select it for the best practice.Open the architecture
05

Tools NGT works with across clouds

Chosen per customer; most estates already run some of them.

Clouds

awsazuregoogle-cloudhuawei-cloudalibaba-cloud

Infrastructure as code

terraformaws-cdkCloudFormationansiblepuppetChefcrossplane

Containers and delivery

kubernetesamazon-eksaksdockerhelmargogitlabgithubjenkinsazure-devopsaws-codepipelinebitbucket

Operations

opentelemetryprometheusgrafanagrafana-lokigrafana-tempodatadogSplunkservicenow

Security and secrets

vaultazure-key-vaulttrivysonarqube
SourcesNGT Service Offering v2.0 (Mar 2025)NGT Service Offering v3.2 (Jul 2026)NGT DevOps–AI Service Offering (Oct 2026)NGT Azure Service Offering v1.0 (Dec 2024)NGT Google Cloud Service Offering v0.1NGT Cloud Operation Service Offering v0.2 (Jan 2025)FPT Software AWS Cloud Journey Service Offering V3FPT Software Cloud Transformation Capabilities (2024)FleziLift method and runbook (Oct 2026)