LigaBet AWS Migration Case Study

Solution

Automated capability to create new workload accounts

LigaBet intends to serve its clients as a PaaS (Platform as a Service) solution. For each new customer, new AWS Accounts must be created based on their production infrastructure/environment. As Kloia, we suggested an IaC approach with Terraform for this case. The AWS resources that must be produced for each client have been specified as a Terraform Module and version controlled in their respective Terraform Cloud Private Registry.

Multi Cluster Management - Rancher

When Amazon EKS is used with Rancher, its user-friendliness is combined with AWS's capabilities, reliability, and performance. Each of the workload accounts has an EKS cluster, and a centralized management for them was required. We created a Rancher management account and Rancher has been set up on an Upstream RKE2 Cluster that we constructed for the administration of the Downstream EKS Clusters.

Cost Optimization - Running their dev and staging workloads at a lower cost.

For non-critical tasks, it is advantageous to use EC2 Spot instances to optimize costs. We designated environments for staging and development as non-critical workloads. After a few months of development and staging, EC2 expenditures were reduced by about 60 percent compared to a standard production account.

In-house Serverless CI/CD Pipeline

LigaBet has a set of workloads that consists of legacy Windows applications. Unfortunately the updating mechanics are fairly complicated for these applications. The search for a suitable CI/CD tool was in vain, so we created an in-house CI/CD Pipeline with AWS Step Functions. 

This custom CI/CD Pipeline supports rolling updates on live hosts and it also creates EC2 Images to use with Auto Scaling Groups at the same time. 

Central Security

GuardDuty and Config were enabled in the Security Account as delegated administrators for compliance, audit, and threat detection. GuardDuty and Config data are sent to the Security Account from all other accounts in the organization. This allowed the team to centrally track security issues for all accounts within the organization. If a new account is added in the future, that account will send GuardDuty and Config data to the security account automatically.

Centralized Log Management

We have created an AWS Log Account for centralized logging. 

• We have created log export logic using the AWS Step Functions for the managed services and CI/CD pipeline components. It exports cloudwatch logs to an S3 log bucket in the Log Account. These logs are also accessible in their own Cloudwatch logs. 
• We have used the CloudWatch agent for the application logs that run on the EC2 instances. The Cloudwatch agent directly exports the application logs to the log account's cloudwatch.