Cloud Transformation

A New Product Platform on AWS

CloudFront and AWS WAF at the edge, containers on ECS or EKS, Aurora and ElastiCache behind, pipelines and code from day one.

The shape NGT starts from when a product is built new on AWS. Traffic enters through Route 53, CloudFront and AWS WAF to a load balancer in front of containers on Amazon ECS with Fargate, or Amazon EKS where Kubernetes is needed. Data sits in Aurora PostgreSQL, ElastiCache and S3 under KMS keys, and every environment comes from a pipeline and Terraform or AWS CDK.

HTTPSfiltersoriginSQLsessionskeysmetrics, logssnapshotspushimagedeployprovisionsaccountsAWS CloudEdge · global servicesObservability, keys and secretsVPC · two Availability ZonesPublic subnetsPrivate subnets · applicationPrivate subnets · dataDelivery · pipelines and infrastructure as codeCustomersweb and mobileProduct teampush codeAmazon Route 53Amazon CloudFrontAWS WAFAmazon CloudWatchAWS X-RayAWS KMSAWS Secrets ManagerApplication LoadBalancerAmazon ECSon AWS FargateAmazon EKSwhere Kubernetes is neededAmazon AuroraPostgreSQLAmazon ElastiCacheAmazon S3files and static assetsAWS Backupplans per tierAWS CodePipelineAWS CodeBuildAmazon ECRTerraform or AWS CDKevery environment as codeAWS Control Toweraccounts from the landing zone

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

  • A new product or SaaS platform that must reach production quickly
  • Development and production that must stay clearly apart
  • A team that wants releases without manual steps and with automatic rollback

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