Automated spin-up of Amazon Web Services and Azure accounts using GitLab Pipelines

Case Study

Automated spin-up of Amazon Web Services and Azure accounts using GitLab Pipelines

ITGix Team
ITGix Team
Passionate DevOps & Cloud Engineers
20.03.2023
Reading time: 2 mins.
Last Updated: 19.04.2023

Table of Contents

A Swiss-based technology company contacted ITGix to build an end-to-end automation solution that will be used to spin up individual AWS or Azure accounts, deploy all necessary infrastructure and application services, and set up automated monitoring for all components.

A Swiss-based technology company providing automated application, product, and workflow-building solutions has contacted ITGix.

The client needed an end-to-end automation solution that will be used to spin up individual AWS or Azure accounts, deploy all necessary infrastructure and application services, and set up automated monitoring for all components. Additionally, all applications would be containerized and communicate with each other via REST API calls.

THE CHALLENGE

The biggest challenge in the project was the requirement to automate the installation, configuration, and monitoring of every single component running in the AWS/Azure account. Furthermore, our client needed to be able to spin up a multitude of individual Cloud accounts on-demand without the need for any manual configuration. Each of their subsequent clients would have a pair of AWS or Azure accounts, one for their Non-Production and one for their Production environments.

THE SOLUTION

ITGix implemented a solution for end-to-end automation of all components. We maintained infrastructure as source code and security best practices.

→TERRAFORM MULTI-TENANT ROLE SETUP

1. Management account – stores centralized repositories and user management – Helm Chart repository, Docker Repository, LDAP, Identity Provide

2. Client accounts – set up 2 AWS or Azure accounts for Non-Prod and Prod applications. Includes EKS/AKS cluster and RDS/DB cluster

3. Helm provider integration is used for the automated deployment of applications in the Kubernetes cluster.

4. Automated monitoring and log aggregation setup – Prometheus-operator, OpenDistro/Elasticsearch, Kibana, Grafana

→GitLab CI/CD PIPELINES

1. Application pipelines for building and testing the latest version of the application and pushing containers to the Docker registry and Helm charts to the Helm repository.

2. Infrastructure and application deploy pipelines for executing Terraform in Client accounts.

The final infrastructure setup for a client looked like this:

THE CONCLUSION 

Although there were many challenges in the goal of automating every step of the way, we managed to implement it in its entirety within the initially defined schedule. The Client is already using the automation stack to spin up multiple Cloud environments for their clients. Contact us for expert services.

More Case Studies

A company in the enterprise sector is looking for a partner to migrate a Java Monolith Application to Containerized environment in Amazon Web Services AWS. With the migration, we will...
Reading
Why go for a multi-master setup? To have a truly reliable, highly available distributed system for your applications. Master fault tolerance. Why go for a multi-zone setup? To improve availability...
Reading

Blog Posts

Get In Touch
ITGix provides you with expert consultancy and tailored DevOps services to accelerate your business growth.
Newsletter for
Tech Experts
Join 12,000+ business leaders, designers, and developers who receive blogs, e-Books, and case studies on emerging technology.