Studied by 0 people
Looks like no one added any tags here yet for you.
Migration Strategy
The approach used to migrate a workload into the AWS Cloud.
7 Rs
The seven migration strategies for moving applications to the cloud: Retire, Retain, Rehost, Relocate, Repurchase, Replatform, Refactor or re-architect.
Retire
The migration strategy for applications that you want to decommission or archive.
Common Use Cases for Retire
1. No business value in retaining the application. 2. Eliminate the cost of maintaining the application. 3. Reduce security risks from unsupported OS versions. 4. Retire applications with average CPU and memory usage below 5 percent (zombie applications) or between 5 and 20 percent over 90 days (idle applications). 5. No inbound connection for the last 90 days.
Retain
The migration strategy for applications that you want to keep in your source environment or are not ready to migrate.
Common Use Cases for Retain
1. Security and compliance with data residency requirements. 2. High risk requiring detailed assessment before migration. 3. Dependencies on other applications. 4. Recently upgraded applications. 5. No business value for migrating some applications. 6. Plans to migrate to SaaS. 7. Unresolved physical dependencies on specialized hardware.
Rehost
A migration strategy that involves moving applications to the cloud without significant changes.
Replatform
A migration strategy that involves making some optimizations to the application while migrating it to the cloud.
Relocate
A migration strategy that involves moving applications to a different environment without significant changes.
Repurchase
A migration strategy that involves replacing the existing application with a cloud-native version.
Refactor or Re-architect
A migration strategy that involves modernizing the application during the migration, which is complex and not recommended for large migrations.
Zombie Applications
Applications with an average CPU and memory usage below 5 percent.
Idle Applications
Applications with an average CPU and memory usage between 5 and 20 percent over a period of 90 days.
Utilization and Performance Data
Data used to identify zombie and idle applications from your discovery tool.
Security Risks
Risks associated with operating applications that use unsupported OS versions or components.
Data Residency Requirements
Legal obligations to keep data within specific geographic boundaries.
Technical Refresh
An upgrade or update to a system that may postpone migration.
SaaS
Software as a Service, a model where applications are hosted by a vendor and accessed via the internet.
Specialized Hardware
Hardware that does not have a cloud equivalent, often found in specific industries like manufacturing.
Mainframe Applications
Applications that require careful assessment and planning before migrating to the cloud.
Mid-range Applications
Applications that also require careful assessment and planning before migrating to the cloud.
Non-x86 Unix Applications
Applications that require careful assessment and planning before migrating to the cloud.
Mainframe or mid-range applications
These applications require careful assessment and planning before migrating them to the cloud. Examples include IBM AS/400 and Oracle Solaris.
Performance
You might want to retain applications based on their performance, such as keeping zombie or idle applications in your source environment.
Rehost
This strategy, also known as lift and shift, involves moving applications from your source environment to the AWS Cloud without making any changes to the application.
Rehost strategy benefits
You can migrate a large number of machines from multiple source platforms to the AWS Cloud without worrying about compatibility, performance disruption, long cutover windows, or long-distance data replications.
Downtime in Rehost
The downtime depends on your cutover strategy.
Rehost automation services
You can automate rehosting by using AWS Application Migration Service, AWS Cloud Migration Factory Solution, and VM Import/Export.
Relocate
Using this strategy, you can transfer a large number of servers, comprising one or more applications, from an on-premises platform to a cloud version of the platform.
Relocate strategy examples
You can use this strategy to transfer an Amazon RDS DB instance to another VPC or AWS account.
Relocate strategy benefits
The relocate strategy doesn't require purchasing new hardware, rewriting applications, or modifying existing operations.
Repurchase
This strategy, also known as drop and shop, involves replacing your application with a different version or product that provides more business value.
Repurchase benefits
Repurchasing the application typically reduces costs associated with maintenance, infrastructure, and licensing.
Use cases for Repurchase
Common use cases include moving from a traditional license to SaaS, version upgrades or third-party equivalents, and replacing a custom application.
Moving from traditional license to SaaS
This removes the burden of managing and maintaining the infrastructure and helps reduce licensing issues.
Version upgrades or third-party equivalents
By replacing your existing on-premises application with the vendor's latest version or third-party equivalent in the cloud, you can leverage new features and integrate with cloud services.
Replacing a custom application
You can avoid recoding and re-architecting a custom application by repurchasing a vendor-based SaaS or cloud-based application.
Assessment before purchasing
Before purchasing, you need to assess the application according to your business requirements, especially security and compliance.
Training
The process of educating your team and users with the new system after purchasing an application.
Data Migration
The process of transferring your data to the newly purchased application.
Authentication Integration
Integrating the application into your authentication services, such as Microsoft Active Directory, to centralize authentication.
Networking Configuration
Setting up networking to help secure communication between the purchased application, your users, and your infrastructure.
Replatform
A migration strategy that involves moving an application to the cloud while introducing some level of optimization to operate efficiently, reduce costs, or take advantage of cloud capabilities.
Lift, Tinker, and Shift
Another name for the replatform migration strategy.
Managed Service
A service that is fully managed by a provider, reducing the operational burden on the user.
Serverless Service
A cloud service model where the cloud provider dynamically manages the allocation of machine resources.
End-of-Support Migration Program (EMP)
A program that allows migration of legacy Windows Server applications to the latest supported versions on AWS without code changes.
AWS Graviton Processors
Custom-built processors developed by AWS that can help reduce costs.
Porting Assistant for .NET
An analysis tool that helps port .NET Framework applications to run on Linux operating systems.
Containerization
The process of modernizing applications by migrating virtual machines into containers without making code changes.
AWS App2Container
A migration tool used to modernize .NET and Java applications into containerized applications.
Refactor or Re-architect
A migration strategy that involves moving an application to the cloud and modifying its architecture to leverage cloud-native features for improved agility, performance, and scalability.
Monolith Application
An application that is built as a single, indivisible unit, which can hinder quick product delivery.
Test Coverage
The extent to which the testing process covers the application, affecting the quality and delivery of new features and fixes.
Database Refactoring
The process of modifying a database to separate tables that will be migrated from those that will be retained on premises.
Retire (Description & Use Case)
(AWS Migration Strategy) Decommission and stop using the application.; Application is obsolete and no longer provides value.
Retain (Description & Use Case)
(AWS Migration Strategy) Keep the application on-premises or in its current environment.; Compliance, specific operational needs, or no need to move it to the cloud.
Rehost (Description & Use Case)
(Lift & Shift) (AWS Migration Strategy) Move the application to the cloud with minimal changes.; Fast migration with minimal modifications.
Relocate (Description & Use Case)
(AWS Migration Strategy) Move the application to a different data center or region within the cloud.; Improve performance or meet regulatory requirements.
Repurchase (Description & Use Case)
(AWS Migration Strategy) Replace the application with a cloud-native solution, typically SaaS.; When it's more cost-effective to purchase a new service than to migrate the old one.
Replatform (Description & Use Case)
(AWS Migration Strategy) Make optimizations without changing the core architecture.; Move to the cloud with some improvements like using cloud-managed databases or services.
Refactor/Re-architect (Description & Use Case)
(AWS Migration Strategy) Redesign the application to take full advantage of cloud-native features.; To leverage cloud scalability, microservices, or serverless features. Requires code changes.
