Any journey begins with a first step and that’s exactly the approach this financial service firm had in mind when they asked the AWS experts at Flux7 to come in and help. Specifically, the IT team wanted to start with a small project that would set them up for future success. Using Flux7’s Enterprise DevOps Framework, we were able to help them focus on an achievable first step, the migration of their Atlassian stack to AWS, with a longer term roadmap. Read on as we share this AWS case study.
Our DevOps consultants often get asked about the use of specific technologies and if they would make a good fit for the inquirer’s organization. One of those technologies that we frequently field questions about is HashiCorp Vault. As a result, we think you’ll be interested in this short story of a financial services organization who moved to Vault to improve its secret management system. (For a fuller version of this story, please access the case study here.)
Part 2: How to Make AWS Config Work for You
One of the biggest fears that CIOs of the digital age have is not only server crashes, but the inability to recover the system to its last-known state. This is particularly painful in compliance-heavy industries that are subject to external audits to make sure everything is being performed to industry standards and within federal compliance. AWS Config is a service which picks out a detailed account of what happens with your AWS configuration while giving you the critical ability to go back in time and verify or check the state your AWS resources were at a given point of time.