Cloud Migration Factory on AWS is an AWS Solutions Implementation that helps migrate a large number of servers with CloudEndure Migration in a simplified and expedited way at scale. The solution automates many of the manual, time-consuming tasks that enterprises commonly face in migrating servers from on-premise to the cloud; for example, checking prerequisites on the source machine, installing/uninstalling software on the source and target machine. Thousands of servers have been migrated to AWS using this solution. When customers deploy the solution, its AWS CloudFormation template automatically provisions and configures the necessary AWS services.
The solution also deploys Amazon CloudFront, Amazon API Gateway, AWS Lambda, Amazon Cognito, Amazon S3, and Amazon DynamoDB. To learn more about AWS Cloud Migration Factory Solution, see the AWS Solutions Implementation webpage.
For more information about the implementation guide, please visit the AWS Prescriptive Guidance: https://docs.aws.amazon.com/solutions/latest/aws-cloudendure-migration-factory-solution/welcome.html
For more information about the best practices using this solution, please visit the AWS Prescriptive Guidance: https://docs.aws.amazon.com/prescriptive-guidance/latest/migration-factory-cloudendure
|-deployment/
|-aws-cloudendure-migration-factory-solution.template [ CloudFormation template to deploy the base solution ]
|-aws-cloudendure-migration-factory-solution-automation.template [ Nested CloudFormation template to deploy the remote automation feature ]
|-aws-cloudendure-migration-factory-solution-credentialmanager.template [ Nested CloudFormation template to deploy the credential manager feature ]
|-aws-cloudendure-migration-factory-solution-mgn.template [ Nested CloudFormation template to deploy MGN Lambda ]
|-aws-cloudendure-migration-factory-solution-replatform.template [ Nested CloudFormation template to deploy replatform feature ]
|-aws-cloudendure-migration-factory-solution-tracker.template [ Nested CloudFormation template to deploy migration tracker ]
|-aws-cloudendure-migration-factory-solution-target-account.template [ CloudFormation template to deploy target account IAM roles ]
|-source/
|-backend/ [ folder containing backend code ]
|-lambda_functions [ folder containing all lambda function, each sub folder is a lambda function ]
|-lambda_layers [ folder containing all lambda layers, each sub folder is a lambda layer used in one or more lambda functions as defined in the CloudFormation templates ]
|-lambda_unittests [ folder containing lambda function unit tests ]
|-frontend/ [ folder containing frontend code ]
|-Tools Integration/ [ folder containing tool integration code ]
The following unit testing frameworks are used in the solution.
Libraries jest with babel are used for all unit tests involving the front end code. The configuration of jest and babel is maintained in the following solution files:
|-source/
|-frontend/
- babel.config.js [ babel transformation configuration ]
- jest.config.js [ jest transformation configuration ]
All unit test scripts should be created in the same folder as the script or module that they are testing against. When naming the unit test script the format should be as follows:
[original script name].test.js - example for the script Audit.js the test script filename should be Audit.test.js
By default, the jest configuration will produce a coverage report when run and which will be processed using the jest-sonar-reporter Results Processor in order to output a generic report format that can be ingested into SonarQube. A readable version is also output to source/frontend/test-report.xml.
Before running frontend unit tests, jest needs to be installed using the following command, this will install jest and enable it to be run globally from the command line:
npm install jest -global
To run the unit test, ensure the working directory is set to /source/frontend and run the command:
jest ./
python unittest is used alongside the moto library to run unit tests against the Lambda function code within the solution. All python unit tests for Lambda functions can be found in the following folder.
|-source/
|-backend/
|-lambda_unit_test
To run the unit test, ensure the working directory is set to the parent directory of the repository
chmod +x ./deployment/run_lambda_unit_test.sh
./deployment/run_lambda_unit_test.sh
Confirm that all the unit test pass.
Coverage reports should be output to the same directory as the unit test scripts are stored in order to be picked up by the SonarQube configuration included with the solution.
The solution is configured with a default SonarQube properties file that can be used to initialize the solution into an existing SonarQube environment along with configurations to allow coverage reports to be provided during scanning of the solution. This file is located:
|-/
- sonar-project.properties [ SonarQube project properties file ]
This solution collects anonymous operational metrics to help AWS improve the quality of features of the solution. For more information, including how to disable this capability, please see the implementation guide.
Copyright 2022 Amazon.com, Inc. or its affiliates. All Rights Reserved.
Licensed under the the MIT-0 License. See the LICENSE file. This file is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, express or implied. See the License for the specific language governing permissions and limitations under the License.