Patterns for moving off monolithic application architectures to AWS native architectures
In the earlier sections, we discussed multiple options to create greenfield cloud-native applications using various AWS services. That part is a little easy, as you are starting fresh and so you can use various cloud services as you architect your solutions. However, if you have a huge technical debt in an on-premise environment and want to reduce that by moving over to a cloud platform such as AWS, then it takes more effort and planning.
In recent years, AWS has matured its migration services, methodology, and messaging to make it easier for organizations to not just think of greenfield but even plan for brownfield implementations in AWS. They have a methodology of the 6Rs, which possibly covers every scenario for any workload migration to AWS. The 6Rs that AWS has are Rehosting, Replatforming, Repurchasing, Refactoring/Re-Architecting, Retire, and Retain.
The following is a snapshot of this methodology...