---
title: 'How One Simple DevOps Change Saved Thousands! 💰'
source: 'https://youtube.com/watch?v=dLXqdZPk_oc'
video_id: 'dLXqdZPk_oc'
date: 2026-08-19
duration_sec: 170
channel: 'TechWorld with Nana'
---

# How One Simple DevOps Change Saved Thousands! 💰

> Source: [How One Simple DevOps Change Saved Thousands! 💰](https://youtube.com/watch?v=dLXqdZPk_oc)

## Summary

This video features a DevOps professional sharing a real-world example of how a simple cloud infrastructure change—migrating customer certificates to AWS ACM—saved significant time and money. The speaker emphasizes that while the technical implementation was straightforward, the real challenge lay in managing stakeholders and overcoming resistance to change.

### Key Points

- **Applying Bootcamp Concepts** [00:02] — The speaker discusses how concepts learned in a bootcamp can be applied to introduce new tools and best practices to a team.
- **Certificate Renewal Pain Point** [00:15] — The team faced a lengthy, manual certificate renewal process every 12-24 months, involving multiple people and external vendors, leading to frequent errors and delays.
- **Manual Process Issues** [01:11] — The manual process often resulted in wrong CSR signatures, mismatched fields, and other issues, causing significant operational friction.
- **Migration to AWS ACM** [01:25] — The speaker decided to migrate all customers to AWS ACM, eliminating the need for manual renewals and saving each customer approximately $200 per year.
- **Stakeholder Management** [01:56] — Despite the code change taking only a day or two, the rollout took 1-2 months due to stakeholder concerns, requiring clear plans, testing evidence, and team references.
- **IT is About People and Procedures** [02:42] — The speaker concludes that in IT, writing code is the simplest part (especially with LLMs), but the real challenge is managing procedures and people.

## Transcript

where you you knew the concepts from the boot camp that you could actually teach your team or explain to them or kind of introduce maybe suggest them new tools or new ways of doing stuff because you kind of learn that as a best practice.
Like did you have any such examples? >> I have one technologically it was a small change no not much but when it comes to the benefit was huge and that was basically a certificate in the cloud. So when I joined the team we had
the procedure renewal the certificates like every 12 or 24 months and the procedure was very long and it involved a lot of people because basically some
a lot of people because basically some solutions architect from another company had to remind us on Slack that there is a certificate that is due to expire. Then we had to manually create the CSR
to be signed then the CSR had to be sent to the solutions engineer from another team then they had to send it to the certificate authority to be signed then they had to paid for the cert. They need to send it back to us then we had to
upload it. Sometimes they were sending us wrong CSR signs so maybe they were renewing a lot of them. I didn't have like a straightforward procedure to do it. There were a lot of issues along the way with those certs. Sometimes some
fields didn't match some fields has changed and they didn't let us know. I decided to migrate all of the the customers to to the ACM in AWS and the benefit was first of all that we won't need to deal with those renewals anymore
and the second thing every customer would save I don't know how it was would save I don't know how it was around 200 dollars per per year for the certificate renewal. It took me a lot of time to do it even though the the change
in the Terraform code took to write a module and apply it to took me maybe a day or two, but to speak with all of the stakeholders, to speak with all of the customers, I think it was like 1 month or even two. Because people were scared
that well, we've been doing this for years, renewing those thirds. Are you sure it won't break anything? They would bring, you know, head people to the conversations. They wanted to clear plan. What what I'm
going to do if it was tested. They wanted also the names of the teams for this stuff was already deployed. So, it was Yeah, it's like in IT. It's all about the procedures and people, but now especially in coding, right? The
writing code is the is the simplest part right now because we have all of those right now because we have all of those LLMs. It's about the procedures.