AWS mgn documentation change
Summary
Updated references from 'AWS MGN' to 'Application Migration Service' and fixed a documentation link
Security assessment
Changes are purely branding/naming updates without any modifications to security configurations, permissions, or vulnerabilities. The AccessDeniedException note remains unchanged in security context.
Diff
diff --git a/mgn/latest/ug/Troubleshooting-Launch-Errors.md b/mgn/latest/ug/Troubleshooting-Launch-Errors.md index c54fbea87..3f34427aa 100644 --- a//mgn/latest/ug/Troubleshooting-Launch-Errors.md +++ b//mgn/latest/ug/Troubleshooting-Launch-Errors.md @@ -5 +5 @@ -[Documentation](/index.html)[Application Migration Service](/mgn/index.html)[User Guide](what-is-application-migration-service.html) +[Documentation](/index.html)[Application Migration Service](/mgn/index.html)[User Guide](what-is-mgn.html) @@ -32 +32 @@ Use the information in this section to troubleshoot launch errors. -When you save a new template version, it is tagged as the latest version. However, for a multitude of reasons, AWS Application Migration Service (AWS MGN) uses the version marked as the default for its purposes. So in order to actually have AWS MGN recognize the changes you make, you need to go into the template itself, and change the default version to the version you have just updated. +When you save a new template version, it is tagged as the latest version. However, for a multitude of reasons, AWS Application Migration Service (Application Migration Service) uses the version marked as the default for its purposes. So in order to actually have Application Migration Service recognize the changes you make, you need to go into the template itself, and change the default version to the version you have just updated. @@ -45 +45 @@ When you save a new template version, it is tagged as the latest version. Howeve -If you receive an AccessDeniedException error when attempting to log into AWS Application Migration Service (AWS MGN) for the first time and set up your replication settings template, it means that you are not the administrator of your AWS Account and therefore cannot initialize AWS MGN. You must be the Admin user of your AWS Account to initialize AWS MGN. [Learn more about initializing MGN.](https://docs.aws.amazon.com/mgn/latest/ug/mandatory-setup.html) +If you receive an AccessDeniedException error when attempting to log into AWS Application Migration Service (Application Migration Service) for the first time and set up your replication settings template, it means that you are not the administrator of your AWS Account and therefore cannot initialize Application Migration Service. You must be the Admin user of your AWS Account to initialize Application Migration Service. [Learn more about initializing MGN.](https://docs.aws.amazon.com/mgn/latest/ug/mandatory-setup.html) @@ -75 +75 @@ This error mostly occurs when the conversion server is unable to communicate wit -When a test or cutover instance is launched, AWS Application Migration Service (AWS MGN) will attempt to create the latest consistent snapshot of the source server. AWS MGN will wait for all the snapshots to become available and once they are ready, will proceed with the launch workflow. +When a test or cutover instance is launched, AWS Application Migration Service (Application Migration Service) will attempt to create the latest consistent snapshot of the source server. Application Migration Service will wait for all the snapshots to become available and once they are ready, will proceed with the launch workflow. @@ -77 +77 @@ When a test or cutover instance is launched, AWS Application Migration Service ( -If you see a timeout message when launching a test or cutover instance, it means the snapshot creation timed out. In this case, AWS MGN will use the latest successful snapshot for that source server to launch the instance. This ensures you can still launch an instance, but the instance will only contain data current up to the timestamp specified in the message. +If you see a timeout message when launching a test or cutover instance, it means the snapshot creation timed out. In this case, Application Migration Service will use the latest successful snapshot for that source server to launch the instance. This ensures you can still launch an instance, but the instance will only contain data current up to the timestamp specified in the message.