Strategy Recommendations database analysis - Migration Hub Strategy Recommendations

Strategy Recommendations database analysis

Strategy Recommendations automatically identifies the database servers in your portfolio and creates application components for them. For example, if there is a SQL Server database in your portfolio, it's identified as application component sqlservr.exe.

Strategy Recommendations analyzes individual databases in the identified SQL Server application component, sqlservr.exe, using the AWS Schema Conversion Tool. Strategy Recommendations also identifies incompatibilities in migrating the databases to AWS databases such as Amazon Aurora MySQL-Compatible Edition, Amazon Aurora PostgreSQL-Compatible Edition, Amazon RDS for MySQL, and Amazon RDS for PostgreSQL.

Currently, Strategy Recommendations database analysis is only available for SQL Server.

To configure Strategy Recommendations to analyze your databases, you must provide credentials for the Strategy Recommendations application data collector to connect to your databases. To do this, create a secret in AWS Secrets Manager in your AWS account.

For information about the permissions and privileges of the credentials that you provide, see Privileges needed for AWS Schema Conversion Tool credentials. For information about creating a secret with the credentials, see Creating a secret in Secrets Manager for database credentials.

After you set up the credentials and secret, you can configure AWS Schema Conversion Tool analysis on the database server. For information about how to configure analysis, see Configure database analysis for an application component.

After you configure database analysis for the application component, a AWS Schema Conversion Tool inventory task is scheduled. After this task completes, you'll see the new application components being created for every individual database on that database server. For example, if your SQL Server has two databases (exampledbs1 and exampledbs2), an application component is created for each of the databases with the names exampledbs1 and exampledbs2.

If you would like to see anti-patterns in migrating each identified database to AWS databases, set up analysis for each database following the steps in Configure database analysis for an application component.

Privileges needed for AWS Schema Conversion Tool credentials

The username and password that you provide to AWS Secrets Manager only needs VIEW SERVER STATE and VIEW ANY DEFINITION privileges. Optionally, you can create a new login by using the script available at https://gitlab.aws.dev/dmaf-pub/dmaf/-/blob/master/create_mssql_ro_user.sql.

You can provide any login name and password that you want when creating the SQL Server login.

Creating a secret in Secrets Manager for database credentials

After the credentials are ready for the Strategy Recommendations application data collector to connect to a database, create a secret in AWS Secrets Manager in your AWS account as described in the following procedure.

To create a secret with AWS Secrets Manager in your AWS account

  1. Using the AWS account that you created in Setting up Strategy Recommendations, sign in to the AWS Management Console and open the AWS Secrets Manager console at https://console.aws.amazon.com/secretsmanager/.

  2. Choose Store a new secret.

  3. Select the secret type as Other type of secrets.

  4. Under Specify the key/value pairs to be stored in this secret for Secret key-value pairs, enter the following key-value pair.

    username - your-username

    Then choose + Add row and enter following key-value pair.

    password - your-password

  5. Choose Next.

  6. Enter Secret name as any string with the prefix migrationhub-strategy-. For example, migrationhub-strategy-one.

    Note

    Store your secret name in a safe place for later use.

  7. Choose Next, and then choose Next again.

  8. Choose Store.

You can use the secret you created for database credentials when setting up database analysis in Strategy Recommendations.