AWS Cloud    Landing Zones  

The Challenge

HomeMade Digital managed a single AWS account containing all test and production infrastructure, and workload resources were deployed manually over several years. They sought to deploy the “Conversions API Gateway,” a standalone product from Meta. This Kubernetes-based deployment was self-hosted on the customer’s AWS EKS cluster instance.

Furthermore, the Conversions API needed to be hosted in multiple regions, initially with Australia and the UK. Additionally, they required network access from a central deployment server to the clusters in each region.

Additionally, HomeMade Digital recognised that relying on a single AWS account and manual deployments was not recommended, so they sought guidance on deploying their new application on EKS. They also wanted a clear path for migrating their existing applications to align with AWS best practices.

The Solution

MakeCloud deployed the AWS Control Tower solution to create a best-practice, multi-account AWS environment. We implemented SSO, automated account provisioning, and standardized blueprints to ensure consistent best practices across all accounts.

In addition, for networking, we set up a multi-region VPC network using AWS Transit Gateway and deployed networking and EKS through Terraform.

The Result

Through implementing AWS Control Tower, MakeCloud established a new AWS account structure for HomeMade Digital, allowing them to separate production from non-production workloads and create dedicated AWS accounts for backups and audit logging.

Additionally, by leveraging AWS VPC and AWS Transit Gateway, MakeCloud deployed a robust global network infrastructure. This enabled HomeMade Digital to launch their new product in multiple regions, increasing speed to market and enhancing operational efficiency.