Architecture overview - AWS CloudEndure Migration Factory Solution

Architecture overview

Deploying this solution builds the following serverless environment in the AWS Cloud.


        AWS CloudEndure Migration Factory Solution architecture diagram

Figure 1: AWS CloudEndure Migration Factory Solution architecture

The solution’s AWS CloudFormation template launches the AWS services necessary to help enterprises migrate their servers. The template deploys Amazon Elastic Container Service (Amazon ECS) to build a web interface and uploads the code to an Amazon Simple Storage Service (Amazon S3) bucket.

Note

The AWS CloudEndure Migration Factory Solution uses a migration execution server which is not a part of the AWS CloudFormation deployment. For more details on manually building the server, refer to Build a Migration Execution Server.

The solution also configures an Amazon API Gateway to receive migration requests from the migration execution server via RestAPIs, AWS Lambda functions to provide the necessary services for you to log in to the web interface, perform the necessary administrative functions to manage the migration, and connect to third party APIs to automate the migration process.

The user Lambda function ingests the migration metadata into an Amazon DynamoDB table. Standard HTTP status codes are returned to you via the RestAPI from the API Gateway. An Amazon Cognito user pool is used for user authentication to the web interface and RestAPIs.

The tools Lambda functions processes external RestAPI and calls the CloudEndure Migration for AWS migration, and initiates WIG (workload ingestion) RFC (request for change) calls to AWS Managed Services (AMS) for AMS migration. The migration metadata stored in Amazon DynamoDB is routed to CloudEndure using a CloudEndure API to trigger a migration job and launch servers housed in CloudEndure. If your migration target is AMS, the tools Lambda function will automatically initiate an AMS RFC to automate the workload ingestion process to ingest your servers into the AMS production environment.

Optional migration tracker

This solution also deploys an optional migration tracker component that tracks the progress of your migration.

Optional migration tracker component

Figure 2: Optional migration tracker component

The CloudFormation template deploys AWS Glue to get the migration metadata from the CloudEndure Migration Factory DynamoDB table and exports the metadata to Amazon S3 twice a day (at 5:00 AM and 1:00 PM UTC). After the AWS Glue job completes, an Amazon Athena save query is initiated, and you can set up Amazon QuickSight to pull the data from the Athena query results. You can then create the visualizations and build a dashboard that meets your business needs. For guidance on creating visuals and building a dashboard, refer to Build a migration tracker dashboard.

This optional component is managed by the Tracker parameter in the CloudFormation template. By default, this option is activated, but you can deactivate this option by changing the Tracker parameter to false.