A cloud migration, and the ability to take advantage of cloud benefits such as greater agility, scalability and enhanced security, is often seen as a primary way that organizations can positively affect change and create greater productivity at optimized cost. Yet, there are many approaches to large-scale cloud migration, which can be overwhelming, especially for large enterprises with a myriad of business-critical applications. As a result, Flux7 has created a series of short papers designed to walk readers through creating a custom approach to their own cloud migration strategy, in support of strategic business change. Sign up for the full series here and read on for highlights of what’s to come.
Cloud Migration Framework
As an organization begins looking at its larger technology landscape through the lens of cloud computing and strategic change, several options emerge. For companies that want to centralize and standardize their infrastructure in order to reduce overall system maintenance, grow GRC and reduce costs, there are four distinct migration approaches and three non-migration choices: Rehost, Reinstall, Replatform, Refactor, Repurchase, Retain and Retire. Each of these options presents its own benefits and drawbacks which must be considered on an application-by-application basis. The first paper in our series walks readers through these choices, their pros and cons, and how to effectively assess migration paths for cloud.
AWS Cloud Migration Case Study
The second piece in our series shares several stories of how the cloud migration framework was applied to achieve a tailored cloud migration strategy. One such example is Technip, a renewable energy leader that had two parallel goals: It wanted to use an AWS cloud migration strategy as an opportunity to overhaul its business processes and in the migration process, Technip looked to build standardization.
Technip aimed to increase developer agility, grow global access for its workers and decrease capital expenses. While time was of the essence, and Technip had a desire to move the enterprise wholesale to AWS, a reinstall approach was pursued. Following the migration, IT transformation was championed, especially once standardization had been achieved.
The project began with Flux7’s AWS migration experts reviewing critical data about the applications to be moved, and designing push button deployment frameworks which were then used to quickly select and stand up new environments, allowing the client’s DevOps team to focus their efforts on specific applications and not the foundational policies that are part of the AWS automation. The teams moved one application at a time into AWS, starting with a residential solar monitoring Web app.
In order to introduce standardization and maintain separation of duties, the Flux7 team introduced AWS Service Catalog, where 80% of applications are able to be defined by a small number of templates. In this way, the energy company was able to standardize builds with security controls built in, encouraging best practices to be followed by default. And, in order to streamline DevOps, AWS was used to create multiple environments for each team, increasing speed to market and operational efficiencies.
The Flux7 Enterprise DevOps Framework
Next in the series we explore how the Flux7 Enterprise DevOps Framework can be an effective foundation for migrating applications and creating the needed infrastructure to effectively support them in the cloud. We specifically delve into the role of the Landing Zone and how it acts as a critical beachhead in allowing teams to work in parallel, speeding the success of pilots or other proofs of concept.
Last, we discuss cloud sandbox as a strategic enabler. Flux7, an AWS consulting partner, recommends creating secure sandbox environments as organizations start down the path to a cloud migration, as they can help prioritize migration targets and can generally shed light on the benefits cloud computing will bring to different applications.
Naturally, we want to see your cloud migration strategy to a fruitful conclusion, so we’ve also shared several best in breed support tips. Interested in subscribing to the series? Join us here. And, for additional DevOps and IT Modernization news, AWS case studies, and more subscribe to the Flux7 DevOps blog.