Editing the post-launch settings template

AWS MGN supports post-launch modernization actions, giving you the opportunity to move and improve. The service provides a variety of out-of-the-box actions that you can execute on your EC2 launch instances, as well as allows you to create your own actions.

The actions described in the following sections can be edited within the post-launch template. Once you have edited your settings, choose Save template.

Activating and deactivating post-launch actions

This setting controls whether post-launch actions are activated or deactivated. You must leave the Install System Manager agent and allow executing actions on launched servers option toggled in order for post-launch actions to work. Untoggling the option will disallow AWS MGN to install the SSM Agent on your servers and post-launch actions will no longer be executed on them.

Deploying post-launch actions

Use this setting to choose whether to execute the post-launch actions on your cutover instances, on your test instances, or on both cutover and test instances.

Note

Only trusted, authorized users should have access to parameter store. For enhanced security, ensure that users who do not have permissions to execute SSM documents/commands, do not have access to parameter store. Learn more about restricting access to Systems Manager parameters.

Encrypt post-launch action parameters

The post-launch action parameters are stored in AWS Systems Manager (SSM) Parameter Store . For enhanced security, ensure that users who do not have permissions to execute SSM documents, do not have access to the Parameter Store. For an additional layer of security you can select to encrypt the action parameters using AWS Key Management Service (KMS) encryption.

AWS SSM encrypts the parameter value of SecureString parameters type using AWS KMS with an AWS managed key or with the default KMS key provided by AWS. You can specify different keys for each parameter, or use the same key for multiple parameters.

Post-launch actions table

The post-launch actions table includes both predefined actions and custom actions that will be executed on your new EC2 instances.

• Predefined post-launch actions are provided out of the box. They are prepopulated with the necessary values and only need to be activated or deactivated. These actions are based on public SSM documents that cannot be changed and have certain unchangeable parameters such as the platform name and order.

• Custom post-launch actions are based on SSM documents that you create and upload to your account.

Use the Filter by options on the left-hand side to filter the available actions according to your preferences.

Click the settings icon in the right-hand corner of the screen to alternate between card and list view, according to your preferences.