AWS solutions documentation change
Summary
Updated documentation links for building migration automation server and importing migration metadata
Security assessment
Changes only update hyperlinks to other documentation pages without modifying security content, configurations, or best practices. No security vulnerabilities or weaknesses are addressed.
Diff
diff --git a/solutions/latest/cloud-migration-factory-on-aws/components.md b/solutions/latest/cloud-migration-factory-on-aws/components.md index 62da06e8d..83576be5a 100644 --- a//solutions/latest/cloud-migration-factory-on-aws/components.md +++ b//solutions/latest/cloud-migration-factory-on-aws/components.md @@ -13 +13 @@ Migration automation serverMigration services Rest APIsMigration Factory web int -This solution leverages a migration automation server to run migrations using Rest APIs. This server isn’t automatically deployed with the solution and must be built manually. For more information, refer to [Build a Migration Automation Server](./step7.html). We recommend that you build the server in your AWS environment, but you can also build on-premises in your network environment. The server must meet the following requirements: +This solution uses a migration automation server to run migrations using Rest APIs. This server isn’t automatically deployed with the solution and must be built manually. For more information, refer to [Build a Migration Automation Server](./configure-migration-automation-server.html). We recommend that you build the server in your AWS environment, but you can also build on-premises in your network environment. The server must meet the following requirements: @@ -60 +60 @@ Log in services include the `login` Lambda functions and Amazon Cognito. Once yo -Admin services include the Amazon API Gateway, `admin` Lambda functions, and Amazon DynamoDB. Administrators for the solution can use the `admin` Lambda function to define the migration metadata schema, which are the application and server attributes. The admin services API provides the schema definition for the DynamoDB table. User data including application and server attributes must adhere to this schema definition. Typical attributes include the `app_name`, `wave_id`, `server_name`, and other fields as identified in [Import migration metadata into the factory](./step8.html#import-migration-metadata-into-the-factory). By default, the AWS CloudFormation template deploys a common schema automatically, but this can be customized after deployment. +Admin services include the Amazon API Gateway, `admin` Lambda functions, and Amazon DynamoDB. Administrators for the solution can use the `admin` Lambda function to define the migration metadata schema, which are the application and server attributes. The admin services API provides the schema definition for the DynamoDB table. User data including application and server attributes must adhere to this schema definition. Typical attributes include the `app_name`, `wave_id`, `server_name`, and other fields as identified in [Import migration metadata into the factory](./test-solution-automation-scripts.html#import-migration-metadata-into-the-factory). By default, the AWS CloudFormation template deploys a common schema automatically, but this can be customized after deployment.