Tosin Ojediran is a DevOps Engineer at a FinTech company – one of three people on the entire DevOps team. The small team’s resources are stretched as they maintain the company’s cloud infrastructure and integrations. Not only that, but the business is scaling rapidly – which means the infrastructure is constantly growing.
In the midst of this growth, the CTO approached Tosin and pointed out the rapid growth in the Amazon Web Services (AWS) bill, and told him they had to reduce it or Finance would come after them.
At first, Tosin’s team toyed with the idea of reducing the number of nodes – although given the developers’ aggressive objectives, taking away some of the computing capacity was hardly ideal. They also considered switching to another cloud provider to get cheaper rates – but not only did they not have the time to migrate, they weren’t sure how much money the move would actually save.
As they considered their options, they realized that many servers were running during hours they weren’t needed, like nights and weekends. The team thought about writing scripts to schedule these off times – but that would take time away from their core projects, and require maintenance as their infrastructure continued to grow. Plus, any time they spent on the project would be an additional overhead cost.
They searched to find a tool that would automate the scheduling. Their criteria were: quick implementation and easy integration, with a reasonable payback period.
Tosin searched online for an AWS optimization or scheduling tool, and found a blog post that mentioned some cost reduction tips (like Auto Scaling) as well as ParkMyCloud. He started a free trial and saw how simple it would be to create and apply schedules for his instances. Even better, it was simple to set up – as a SaaS tool, ParkMyCloud required none of the scripting and integration time that Tosin had come to expect when setting up new tools.
Tosin also appreciated the fact that anyone can use ParkMyCloud. The simple interface means that no programming or technical knowledge is required. Previously, team analysts and others outside of the DevOps team had to call Tosin and ask him to start their instances when they needed to use them. Using ParkMyCloud’s role and team structures, he gave access to these users so they had direct control to turn their own instances on/off as needed, without exposing other teams’ resources.
After comparing ParkMyCloud to some of the other tools and cost savings tips mentioned in the blog post, Tosin decided to go ahead and sign up.
Using ParkMyCloud, Tosin’s company has reduced their AWS bill by 25-30%. The Finance team is pleased, as is their CTO – in fact, when Tosin sent a savings report to the CTO, he said, “wow, this is awesome.”
Tosin has also freed up some of his own time, by giving AWS users outside of the DevOps team direct access to their AWS instances, eliminating the need for him to constantly act as a middle man. With automated policies, all new instances are immediately put on schedules and assigned to the correct users and teams.
ParkMyCloud was up and running in less than 10 minutes, was easy to integrate, and easy to use. Between the time saved and the money saved, Tosin has found his DevOps solution to control cloud costs. Tosin has verifiable proof of the cost reductions to show his CTO – along with the fact that the savings are being achieved without sacrificing resources, productivity or output. Everyone’s happy.
Download this case study
About FinTech DevOps Team
This company in the FinTech industry wishes to remain anonymous.