Flux7 DevOps consultants have worked with more than 150 companies over the years as they have gone through the DevOps transformation process. And, we’ve learned a lot along the way, including the patterns that emerge in the DevOps journey and where most people land and/or have the vision to land. We’d like to share that journey with you today and more importantly, how we’d encourage you to think about the DevOps framework that helps gets your organization there.
AWS recently introduced the ability to build an end-to-end release automation workflow that can deploy changes across multiple regions or different AWS accounts. And they subsequently featured an article on their blog on the steps to create a cross region CodePipeline. Today, however, we want to address the other half of this equation -- building cross account pipelines -- and thought it worthwhile to share with you here when and why we would recommend the benefits of this approach.
Where does code end and configuration begin? It’s a perennial question. And, as the lines continue to blur between the two we here at Flux7 have begun defining new terminology and ways of thinking of the issue that we’d like to propose in our blog today. As part of a community of developers whose work often entrenches them in these issues, we greatly appreciate your feedback and help in fine-tuning these definitions for the betterment of our collective work.
Continuing with our recent theme of Flux7’s DevOps approach and best practices, today we will discuss the Flux7 microservices philosophy. While we’ve previously defined microservices and their benefits, we are taking a step back today to look at the bigger picture and how one might view and approach microservices for best results.
As systems become more complex, it’s more important than ever to ensure you have a strategy for effective and efficient secrets management. While we will dive into the technical aspects of doing just this within AWS, let’s first review what exactly secrets are and why you need to manage them.
At re:Invent 2016, AWS announced Organizations, the ability to have and easily manage multiple accounts. Flux7 consultants have long recommended multiple accounts to clients as a best practice for maintaining separation of roles and applications to address security and compliance policies and now it’s even easier with the AWS Organizations Service. Let’s first walk through what makes it so easy and then we’ll share AWS and Flux7 best practices.
We work with a variety of healthcare companies and recently had the opportunity to work with one who brings the fun of fitness to customers. This firm pairs motivational workouts with gamification elements to ensure that its customers attain health and fitness.
We are excited to announce that one of our customers, TechnipFMC, a world leader in project management, engineering, and construction for the energy industry, has been featured as an AWS case study. TechnipFMC had a specific challenge they were looking for help with when they called the AWS consultants at Flux7. Specifically, they were looking to ensure security and compliance for its global sites and the perimeter networks that support its client-facing applications.
At Flux7, our big, hairy, audacious goal is to keep our customers exceedingly happy -- falling over themselves happy. And, that doesn’t start by forcing them into a mold or a pre-defined box. As a DevOps consulting company, we sit in the enviable position of getting to focus wholly on helping our customers address their specific business needs.