MGN - AMI in EC2 Launch Template

Hi Team Any response to this would be highly appreciated

The selection of an Amazon Machine Image (AMI) in the Launch Template during migration depends on your licensing strategy in the AWS Cloud. There are two main options:

1. Bring Your Own License (BYOL): If you want to use your existing licenses (BYOL), you don't need to select an AMI in the Launch Template. In this case, the AWS Application Migration Service (MGN) uses a temporary AMI for the migration process.

2. AWS Included License (Pay-As-You-Go): If you prefer to use the AWS Included License (PAYG) model, you must select an AMI in the Launch Template based on the operating system version you are migrating. For example, if you are migrating Red Hat Enterprise Linux (RHEL) 8.x from on-premises to AWS Cloud and want to use the AWS Included License, you need to select the corresponding RHEL 8.x AMI in the Launch Template.

You can refer blog to migrate RHEL instance from On-premises directly into AWS Included license with use of AMI in launch template.

https://docs.aws.amazon.com/prescriptive-guidance/latest/patterns/migrate-rhel-byol-systems-to-aws-license-included-instances-by-using-aws-mgn.html