Cloud Migration Factory FAQ

This section provides answers to commonly raised questions about deploying and using Cloud Migration Factory.

How do I know if this solution is suitable for my project?

Cloud Migration Factory is suitable for customers who have more than 100 servers that they want to rehost on AWS. Those servers must also be within the list of supported operating systems for AWS Application Migration Service.

How much does it cost to run Cloud Migration Factory?

Cloud Migration Factory is a serverless solution that uses AWS services such as Amazon Simple Storage Service (Amazon S3), Amazon CloudFront, Amazon DynamoDB, and AWS Lambda. Your cost depends on your usage.

How can I deploy or get support for Cloud Migration Factory?

To deploy Cloud Migration Factory, see the AWS Cloud Migration Factory Solution on the AWS Solutions website. The source code is available in a GitHub repository. If you have any questions, email AWS Professional Services at [e-mail]. We will be happy to help you.

After I deploy Cloud Migration Factory, can AWS help me migrate my servers using this solution?

Yes, the AWS Professional Services team can help you. Please email us at [e-mail] and tell us about your use cases. This process includes:

• An initial conversation to discuss your business case

• A one-hour Cloud Migration Factory introduction and demo session with your team

• Migration immersion day with Cloud Migration Factory, including a half-day lab session followed by Q&A

• Discussion of resources you might need from AWS Professional Services

What permissions do I need to deploy the migration factory solution?

Ideally, you will need to use AWS administrator credentials to deploy the stack. If not, we can provide AWS Identity and Access Management (IAM) policies for you to attach to the user who will deploy the factory.

What permissions do I need to run the automation scripts?

For Windows, you need a domain user with local administrator credentials to access all Windows servers. For Linux, you need a sudo user with NOPASSWD enabled.

What firewall rules do I need to create for the migration execution server?

The migration execution server needs to access source servers and external APIs (AWS Application Migration Service, Cloud Migration Factory, and AWS APIs). The server needs access to the internet to access these APIs. You can use a proxy server, but if you do, the proxy server can’t use authentication. The server needs SSH access to the source Linux server on TCP port 22, or Windows Remote Management (WinRM) access to the source Windows server on TCP port 5985.

Can I customize the Cloud Migration Factory schema to capture additional attributes?

Yes, you can modify or extend the schema to capture additional server or application attributes.

Why doesn’t the CSV file include all Amazon EC2 launch template attributes?

Cloud Migration Factory hides uncommon attributes, such as IAM role and public IP. However, you can add these attributes to the CSV file and import them to update the Amazon Elastic Compute Cloud (Amazon EC2) launch templates.

Can I bulk-update the Amazon EC2 launch templates for all my servers?

Yes, you can set hardcoded values for any Amazon EC2 launch template attribute. For example, Cloud Migration Factory sets a private IP for all servers and sets the disk to use gp2 volumes by default, but you can update these attributes.

Does Cloud Migration Factory support SAML federation?

Security Assertion Markup Language (SAML) federation isn’t currently supported.

What should I do if using Launch Server or Check Status in Cloud Migration Factory displays an “Unexpected timeout” error?

If you receive a timeout error, your Cloud Migration Factory login token might have expired. Refresh the web page to get a new token.