This Migration Readiness Assessment is split into 6 perspectives from the AWS Cloud Adoption Framework to assess an organization's migration readiness. The left side is mainly business and the right side is mainly technology-focused.
There may be disconnected or incomplete data in an environment. We have been helping customers by leveraging well established tools and processes, as well as our experience, to build an understanding of the customer’s environment and create a tailored plan that allows for an iterative/agile approach over time.
The plan will include a definition of the migration pattern for each workload. Our consultants will consider the feedback from application stakeholders and draw from their experiences to help determine the appropriate migration patterns.
Rehost (a.k.a. lift and shift) – is focused on maintaining the architecture and migrating directly to a server running in the cloud. This migration can be done manually by copying the data or using automated tools such as CloudEndure.
Replatform – is very similar to rehosting, but the key difference is that the code is altered to take advantage of new cloud infrastructure (a.k.a. Platform-as-a-Service). Some common services include Relational Database Service (RDS) or ElastiCache for Redis.
Repurchase – is moving to a SaaS model.
Refactor – is redesigning the application to be cloud-native. These applications drive the most value out of the cloud. Automation or Serverless approaches provide the most operational efficiencies.
Retire and Retain – are exactly as the names suggest. Mainframes are an example of when customers may retain the application on-prem until the next version of the application can be Repurchased or Refactored.
Presidio recognizes that most customers are at various stages with regards to their adoption of cloud technologies. Maturity Patterns can be split into 4 common states; we help establish a starting point, define positive paths forward, and transition to an optimizing state. By better understanding your maturity, Presidio will be positioned to engage appropriately.
Combining the Migration and Maturity Patterns helps define a road map to evolve cloud operations and applications to maximize the return on investment. Evolution leads to lower operating costs, increased security, and speeds up-time to business value.
Foundational Model is the baseline architecture for the workloads. It covers account structure, network design, IAM, and security at scale. A multi-account approach is recommended to address the soft limits of individual AWS accounts and simplify governance. Core accounts are centralized services to streamline operations at scale. They allow team or group accounts to be created as needed, but you can still maintain an audit trail in the log archive account or allow shared services to be available across the organization. AWS Landing Zone or Control Tower are AWS Solutions that enable organizations to deploy the multi-account approach from pre-configured automation frameworks. You can consider these as easy buttons instead of manually putting together all the building blocks. VMware Cloud on AWS is a VMware managed service offering within AWS facilities. It integrates with existing vSphere environments so VMs can be migrated as-is to maintain workloads and be able to expand to AWS. This Foundational Model allows organizations to continue to use existing VMware skillsets. Application in the Primed Maturity pattern would be a great fit for VMC on AWS.
AWS is responsible for the security of the cloud. This includes the Global infrastructure and services consumed, such as compute, storage, database, and networking. Customers have the choice of security configurations in the cloud. AWS infrastructure has many assurance programs. They span commercial, government, and international standards. Because security in the cloud is the customer’s responsibility, various security services are available to the customer or the customer can leverage their own tools.
There are five best practice areas for security in the cloud:
Traditional IT operating model generally have separate team silos. Each team was responsible for overseeing their own domain and IT operated more like an assembly line. In the cloud operating model, compute, storage, network, and security are defined as software and part of the overall cloud infrastructure. Traditional IT roles must change to support this new operating model.
CCoE is a cross-functional team responsible for developing and managing the cloud strategy within the organization.
The Cloud Business Office exists to ensure alignment of the Cloud goals to the business’s goals and the strategic and tactical execution of them across elements of people, process, and technology in a well-governed and inclusive way.
Enablement Program is designed to address how an organization will get cloud capabilities embedded into skill sets, processes, and culture.
Workload Definitions defines the reference architecture, blueprints, templates, and operating models best suited for a workload. We have defined three principal cloud operating models:
Presidio is excited to help our customers navigate Cloud Migrations to AWS and are ready to help. Please reach out to your account management team for more information.