We use cookies. You have options. Cookies help us keep the site running smoothly and inform some of our advertising, but if you’d like to make adjustments, you can visit our Cookie Notice page for more information.
We’d like to use cookies on your device. Cookies help us keep the site running smoothly and inform some of our advertising, but how we use them is entirely up to you. Accept our recommended settings or customise them to your wishes.
×

Developing Infrastructure as Code for a leading Non-Profit organization

Challenge

A large nonprofit organization sought to build an enterprise data platform. As part of the build, they faced the challenge of maintaining and running multiple data environments. This included a risk of different environmental variables growing over time which typically causes an environment drift. The task to manage this was very manual, time consuming, and slowed down deployments considerably. These inconsistencies between environments could result in deployment issues as well as security vulnerabilities. They needed a system which would help them scale and manage the infrastructure in a consistent and cost-effective manner.

Approach

Ugam, a Merkle company, automated this requirement and developed an end-to-end infrastructure as code (IaC) pipeline. This solved the problem of "environmental drift", and changes were replicated across all environments in a consistent and automated manner. The team created templates for infrastructure resources and applications for quick and reliable provisioning called “stacks”. Also, they now can easily update or replicate the stacks as needed.

Additionally, we enabled collaboration around infrastructure configuration and provisioning, most notably between dev and ops using code. This resulted in reducing the DevOps team from 8 full-time equivalents (FTE) to 2 FTEs. The solution was scalable with newer environments getting deployed at greater speed, less risk, and at a significantly reduced cost. Other notable actions:

  1. Studied the requirements for environment management and frequency of changes

  2. Decided to manage infrastructure via source control

  3. Enabled collaboration around infrastructure configuration and provisioning

  4. Removed the dependency written documentation

 

Results

Streamlined the environmental drift in the release pipeline

Reduced team size from 8 to 2 full-time equivalents

Developed an efficient, cost-effective IaC to provision infrastructure

Keys to success

  • Managed deployment and ongoing maintenance with automated DevOps frameworks
  • Leveraged software engineering tools and practices
  • Developed an end-to-end infrastructure as Code (IaC) pipeline

Discover how we did it. Contact us today.

Contact Us