Migrating to AWS can be complex depending on the number, size and dependencies not just of the applications, but related middleware and infrastructure. To do a proper migration you will need to sort out the infrastructure (AD, LDAP, SSO, File Servers, NFS, DFS) first; move these over first to AWS, then second, migrate the applications and databases (data, machine images). Obviously, you will need to understand the dependencies to do this (an example would be Citrix on premise to Citrix, not AWS, Cloud, middleware, SAN, NAS application dependencies, certificate management etc).
In short, this is best accomplished using native AWS services (Discovery, DMS, SMS), an Agile-Factory approach of cross-company co-operation including integrated testing; operations, the Business Owner, SMEs; based on a complete understanding of dependencies, application and database size and complexity. We will build tranches of similar applications, which the cross-functional team will move over, using standard tools and processes to AWS, and fulfill key requirements. We would also propose setting up a Cloud Center of Excellence (CCOE) governance process (if one does not exist, or if it does, to help with any improvements); to ensure standards and compliance. Cloud projects need a dedicated Cloud Governance model.
For example, a typical migration has common key requirements.
1-Migrate from a DC or Co-Lo in a short period of time to both IaaS and PaaS depending on the DB platform
2-Use AWS Discovery agents, move all related and relevant assets to AWS including Code, Applications, data (application, database), Networking, Security, LDAP, SSO, file servers, NAS, Storage devices,
3-Accomplish the migration using a ‘Factory Approach’ (platform dedicated cross functional Agile-Team) using AWS native tools
4-Ensure there is no business or end-user disruption and migrate according to Principles, a Cloud Environment Strategy
5-Network, setup the receiving environments, security configurations, do a DNS cutover to the new environment and decommission the existing DC or Co-Lo
Current Estate and Future Estate
Process & Approach:
We use the standard AWS CAF approach to migration with a view to ‘accelerating’ the process. We work with our clients on joint teams to do this. Given that most Clients are familiar with this approach, we will not explain every phase in detail. We have a detailed High-Level Design for migrating to AWS which contains the entire stack (networking to application layer, including security). We can share this document with our Client (it is a 30-page template we fill in on our projects).
(Figure: Governance will be best enforced by a CCOE)
1-Set up the CCOE or at least a Project-Governance Team for AWS comprised of CTO, EA’s, TA’s
2-Create a plan for moving the applications and related assets to AWS including tooling, testing, security and the exact process for each platform (e.g. Oracle), timeframes, RAID, RACI, Operational management and Runbooks
3-In parallel create the inter-firm Agile teams which will perform the work who will build out their documentation based on the Master Document (use Jira, Confluence, Agile methods, Scrum etc)
4-Use best practices such as native AWS tools, or existing Client tools as much as possible
The 5 Factory phases for Cloud Migration would include: -
Future (‘Transformed’) Architecture: Automation and the leveraging of infrastructure as code, configuration management techniques to deal with day 2 operational challenges such as server sprawl, configuration drift, fragile infrastructure, software entropy etc. The ‘R’ Strategy depends entirely on what the application is, purpose, end-users, how long lived, and whether it is monetised.