# Using the AWS DMS Fleet Advisor Target Recommendations feature
**Important**
End of support notice: On May 20, 2026, AWS will end support for AWS Database Migration Service Fleet Advisor. After May 20, 2026, you will no longer be able to access the AWS DMS Fleet Advisor console or AWS DMS Fleet Advisor resources. For more information, see [AWS DMS Fleet Advisor end of support](https://docs.aws.amazon.com/dms/latest/userguide/dms_fleet.advisor-end-of-support.html).
To explore and choose an optimal migration target, you can generate target recommendations for your source on-premises databases in DMS Fleet Advisor. A *recommendation* includes one or more possible AWS target engines that you can choose for the migration of your source on-premises database. From these possible target engines, DMS Fleet Advisor suggests a single target engine as the right-sized migration destination and indicates this target as **DMS recommended**. To determine this right-sized migration destination, DMS Fleet Advisor uses the inventory metadata and metrics collected by your data collector.
You can use recommendations before the start of a migration to discover migration options, save costs, and reduce risks. You can export recommendations as a comma separated values (CSV) file, and share it with key stakeholders to facilitate decision making. You can export recommendations into the AWS Pricing Calculator to further optimize maintenance costs. For more information, see [https://calculator.aws/\$1/](https://calculator.aws/#/).
You can't modify target recommendations in DMS Fleet Advisor. Thus, you can't use DMS Fleet Advisor for what-if analysis. *What-if analysis* is the process of changing the target parameters to see how those changes affect the pricing estimate of your recommendation. You can run what-if analysis in the AWS Pricing Calculator using the recommended target parameters as the starting point in the AWS Pricing Calculator. For more information, see [https://calculator.aws/\$1/](https://calculator.aws/#/).
We recommend that you consider the DMS Fleet Advisor recommendation is a starting point in your migration planning. You can then decide to change the recommended instance parameters to optimize the cost or performance of your database workloads.
**Topics**
+ [Recommended target instances](#fa-recommendations-instances)
+ [How does DMS Fleet Advisor determine target instance specifications for the recommendation?](#fa-recommendations-how-it-works)
+ [Generating target recommendations with AWS DMS Fleet Advisor](fa-recommendations-generate.md)
+ [Exploring details of target recommendations with AWS DMS Fleet Advisor](fa-recommendations-view.md)
+ [Exporting target recommendations with AWS DMS Fleet Advisor](fa-recommendations-export.md)
+ [Discovering and analyzing migration limitations with AWS DMS Fleet Advisor](fa-data-collectors-database-features.md)
+ [Troubleshooting for target recommendations with AWS DMS Fleet Advisor](fa-recommendations-troubleshooting.md)
## Recommended target instances
For target recommendations, DMS Fleet Advisor considers the following general purpose, memory-optimized, and burstable performance Amazon RDS DB instances.
+ db.m5
+ db.m6i
+ db.r5
+ db.r6i
+ db.t3
+ db.x1
+ db.x1e
+ db.z1d
For more information about Amazon RDS DB instance classes, see [DB instance classes](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.DBInstanceClass.html) in the *Amazon RDS User Guide*.
## How does DMS Fleet Advisor determine target instance specifications for the recommendation?
DMS Fleet Advisor can generate recommendations based on either database capacity or utilization.
+ If you choose to generate the recommendation based on database capacity, then DMS Fleet Advisor maps the existing database capacity to the specifications of the closest instance class.
+ If you choose to generate the recommendation based on resource utilization, then DMS Fleet Advisor determines the 95th percentile value for such metrics as CPU, memory, IO throughput, and IOPS. 95th percentile means that 95 percent of the collected data is lower than this value. Then, DMS Fleet Advisor maps these values to the specifications of the closest instance class.
To determine the size of the target database, DMS Fleet Advisor collects information about the size of your source database. Then, DMS Fleet Advisor recommends using the same size for the target storage. If your source database storage is overprovisioned, then the recommended size of the target storage will also be overprovisioned.
If you want to migrate data using AWS DMS, then you might need to increase IOPS provisioning for your target DB instance. When DMS Fleet Advisor generates target recommendations, the service considers only your source database metrics. DMS Fleet Advisor doesn't consider additional IOPS that you might need to run data migration tasks. For more information, see [Migration tasks run slowly](CHAP_Troubleshooting.md#CHAP_Troubleshooting.General.SlowTask).
To estimate the IOPS costs, DMS Fleet Advisor uses a one-to-one mapping of your source IOPS usage as a baseline. DMS Fleet Advisor considers the peak load as the baseline value and 100% utilization for IOPS pricing.
For PostgreSQL and MySQL source databases, DMS Fleet Advisor can include Aurora and Amazon RDS DB instances in the target recommendations. If an Aurora configuration maps to the source requirements, then DMS Fleet Advisor marks this option as recommended.
# Generating target recommendations with AWS DMS Fleet Advisor
**Important**
End of support notice: On May 20, 2026, AWS will end support for AWS Database Migration Service Fleet Advisor. After May 20, 2026, you will no longer be able to access the AWS DMS Fleet Advisor console or AWS DMS Fleet Advisor resources. For more information, see [AWS DMS Fleet Advisor end of support](https://docs.aws.amazon.com/dms/latest/userguide/dms_fleet.advisor-end-of-support.html).
After you complete data collection and inventory of your database and analytics fleet, you can generate target recommendations in DMS Fleet Advisor. To do so, choose source databases and configure the settings that the DMS Fleet Advisor Target Recommendations feature uses to determine the size of target instances. Also, the DMS Fleet Advisor Target Recommendations feature uses the capacity and utilization metrics collected from your source databases.
**To generate target recommendations**
1. Sign in to the AWS Management Console and open the AWS DMS console at [https://console.aws.amazon.com/dms/v2/](https://console.aws.amazon.com/dms/v2/).
Make sure that you choose the AWS Region where you use the DMS Fleet Advisor.
1. In the navigation pane, choose **Recommendations** under **Assess**, and then choose **Generate recommendations**.
1. In the **Select source databases** panel, select the check boxes for the names of databases that you want to migrate to the AWS Cloud.
For **Search source databases**, enter the name of your database to filter your inventory.
DMS Fleet Advisor can generate recommendations for up to 100 databases at one time.
1. For **Availability and durability**, choose the preferred deployment option.
To calculate target recommendations for your production databases, choose **Production (Multi-AZ)**. DMS Fleet Advisor includes two DB instances in different Availability Zones in your target recommendation. This Multi-AZ deployment option provides high availability, data redundancy, and failover support.
If Aurora is the recommended target engine and **Availability and Durability** is a Multi-AZ deployment, the target recommendation includes a reader and writer DB instance.
To calculate target recommendations for databases that you use for development or testing, choose **Dev/Test (Single-AZ)**. DMS Fleet Advisor includes a single DB instance in your target recommendation. This Single-AZ deployment option reduces maintenance costs.
1. For **Target instance sizing**, choose the preferred option which DMS Fleet Advisor uses to calculate target recommendations.
To calculate target recommendations based on your source database or OS server configuration, choose **Total capacity**. DMS Fleet Advisor uses such metrics as total CPU, memory, and disk capacity of your source databases or OS servers to generate target recommendations. Then, DMS Fleet Advisor maps your database capacity metrics to the specifications of the closest Amazon RDS DB instance class.
To calculate target recommendations based on the actual utilization of your source database or OS server, choose **Resource utilization**. DMS Fleet Advisor uses utilization metrics of the CPU, memory, and disk capacity of your source databases or OS servers to generate target recommendations. From the utilization metrics, DMS Fleet Advisor computes the 95th percentile for each metric. 95th percentile means that 95 percent of the data within the period is lower than this value. Then, DMS Fleet Advisor maps these values to the closest Amazon RDS DB instance class.
We recommend that you use the **Resource utilization** option for more accurate recommendations. To do so, make sure that you have collected the total capacity and resource utilization metrics.
1. Choose **Generate**.
DMS Fleet Advisor generates target recommendations for the selected databases. For successfully generated recommendations, DMS Fleet Advisor sets the status to **Computed**. Also, DMS Fleet Advisor uses the AWS Pricing Calculator to determine the estimated monthly cost for the recommended target DB instance. Now, you can explore the generated recommendations in detail. For more information, see [Recommendation details](fa-recommendations-view.md).
To estimate the total monthly cost for your data inventory, select the check boxes for databases that you plan to move to the cloud. DMS Fleet Advisor displays the total estimated monthly cost and the summary of your target databases in the AWS Cloud. DMS Fleet Advisor uses the AWS Price List Query API to provide pricing details for your information only. Your actual fees depend on a variety of factors, including your actual usage of AWS services. For more information about AWS service pricing, see [Cloud Services Pricing](https://aws.amazon.com/pricing/).
# Exploring details of target recommendations with AWS DMS Fleet Advisor
**Important**
End of support notice: On May 20, 2026, AWS will end support for AWS Database Migration Service Fleet Advisor. After May 20, 2026, you will no longer be able to access the AWS DMS Fleet Advisor console or AWS DMS Fleet Advisor resources. For more information, see [AWS DMS Fleet Advisor end of support](https://docs.aws.amazon.com/dms/latest/userguide/dms_fleet.advisor-end-of-support.html).
After DMS Fleet Advisor generates target recommendations, you can view the key parameters of the recommended migration target in the **Recommendations** table. These key parameters include the target engine, instance class, number of virtual CPUs, memory, storage, and storage type. In addition to these parameters, DMS Fleet Advisor displays the estimated monthly cost of this recommended migration target.
Each recommendation might include one or more possible AWS target engines. If your recommendation includes several target engines, then AWS DMS marks one of them as recommended. Also, AWS DMS displays the parameters and estimated monthly cost for this recommended option in the **Recommendations** table.
To compare target recommendations to the utilization and capacity of your source database, explore your recommendations in detail. Also, you can view the migration limitations for a selected recommendation. These limitations include unsupported database features, action items, and other migration considerations.
**To explore the recommendation in detail**
1. Generate target recommendations with DMS Fleet Advisor. For more information, see [Generating target recommendations](fa-recommendations-generate.md).
1. Choose the recommendation name from the **Recommendations** table. The recommendation page opens.
1. If your recommendation includes more than one target options, then for **Target recommendations**, choose the target option.
1. Expand the **Source utilization and capacity** section. DMS Fleet Advisor displays resource utilization charts for the following metrics.
+ Number of CPUs
+ Memory
+ I/O throughput
+ Input/output operations per second (IOPS)
+ Storage
+ Number of active database server connections
Use these charts to compare your source database metrics from your DMS data collector to the metrics of the selected target engine.
If you can't see charts after you expand the **Source utilization and capacity** section, make sure that you granted your IAM user with permissions to view Amazon CloudWatch dashboards. For more information, see [Using Amazon CloudWatch dashboards](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch_Dashboards.html) in the *Amazon CloudWatch User Guide*.
1. Choose the link with the name of your selected target engine. The **Target detail** page opens.
1. To export the target recommendations to CSV, choose **Export to CSV** option from the **Actions** dropdown.
1. To export the target recommendations to AWS Pricing Calculator, choose **Optimize cost with AWS Pricing Calculator** option from the **Actions** dropdown.
1. In the **Configuration** section, compare values of your source database parameters to the parameters of the target engine. For the target engine, DMS Fleet Advisor displays the estimated monthly costs for your cloud resources. DMS Fleet Advisor uses the AWS Price List Query API to provide pricing details for your information only. Your actual fees depend on a variety of factors, including your actual usage of AWS services. For more information about AWS service pricing, see [https://aws.amazon.com/pricing/](https://aws.amazon.com/pricing/)Cloud Services Pricing.
1. In the **Migration limitations** section, view the migration limitations. We recommend that you consider these limitations when you migrate your source database to the AWS Cloud.
# Exporting target recommendations with AWS DMS Fleet Advisor
**Important**
End of support notice: On May 20, 2026, AWS will end support for AWS Database Migration Service Fleet Advisor. After May 20, 2026, you will no longer be able to access the AWS DMS Fleet Advisor console or AWS DMS Fleet Advisor resources. For more information, see [AWS DMS Fleet Advisor end of support](https://docs.aws.amazon.com/dms/latest/userguide/dms_fleet.advisor-end-of-support.html).
After you generate target recommendations, you can save a copy of the list of recommendations as a comma-separated value (CSV) file.
**To generate target recommendations**
1. Sign in to the AWS Management Console and open the AWS DMS console at [https://console.aws.amazon.com/dms/v2/](https://console.aws.amazon.com/dms/v2/).
Make sure that you choose the AWS Region where you use the DMS Fleet Advisor.
1. In the navigation pane, choose **Recommendations** under **Assess**, and then select the recommendations to include in your CSV file.
1. Choose **Export to CSV**, enter the file name and choose the folder on your PC where to save this file.
1. Open the CSV file.
The CSV file with recommendations contains the following information.
+ **CreatedDate** – The date when DMS Fleet Advisor created the target engine recommendation.
+ **DatabaseId** – The identifier of the source database for which DMS Fleet Advisor created this recommendation.
+ **DeploymentOption** – The deployment option for the recommended Amazon RDS DB instance.
+ **EngineEdition** – The recommended target Amazon RDS engine edition.
+ **EngineName** – The name of the target engine.
+ **InstanceMemory** – The amount of memory on the recommended Amazon RDS DB instance.
+ **InstanceSizingType** – The size of your target instance.
+ **InstanceType** – The recommended target Amazon RDS instance type.
+ **InstanceVcpu** – The number of virtual CPUs on the recommended Amazon RDS DB instance.
+ **Preferred** – A Boolean flag that indicates that this target option is recommended.
+ **Status** – The status of the target engine recommendation.
+ **StorageIops** – The number of I/O operations completed each second (IOPS) on the recommended Amazon RDS DB instance.
+ **StorageSize** – The storage size of the recommended Amazon RDS DB instance.
+ **StorageType** – The storage type of the recommended Amazon RDS DB instance.
+ **WorkloadType** – The deployment option for your target engine such as Multi-AZ or Single-AZ deployment.
# Discovering and analyzing migration limitations with AWS DMS Fleet Advisor
**Important**
End of support notice: On May 20, 2026, AWS will end support for AWS Database Migration Service Fleet Advisor. After May 20, 2026, you will no longer be able to access the AWS DMS Fleet Advisor console or AWS DMS Fleet Advisor resources. For more information, see [AWS DMS Fleet Advisor end of support](https://docs.aws.amazon.com/dms/latest/userguide/dms_fleet.advisor-end-of-support.html).
You can use the DMS data collector to discover database features that your target engine doesn't support. To choose the right migration target, you should consider these limitations.
The DMS data collector discovers specific source database features. Then, DMS Fleet Advisor analyses source features from a migration standpoint to the specified target and provides additional information about the limitation and includes recommended actions to address or avoid this limitation. Also, DMS Fleet Advisor calculates the impact of these limitations.
The list of limitations is available in the **Target engine details** page. Navigate to this page from the **Recommendations** page in the left navigation menu. From the list of targets, choose the target engine to examine. The list of limitations is at the bottom of the page.
The following table includes MySQL database features that Amazon RDS for MySQL doesn't support.
| Limitation | Description | Impact |
| --- | --- | --- |
| Authentication plugins | Amazon RDS doesn't support MySQL authentication plugins. | Low |
| Error logging to the system log | Amazon RDS doesn't support writing the error log to the system log. | Low |
| Global transaction identifiers | You can use global transaction identifiers with all RDS for MySQL 5.7 versions, and RDS for MySQL version 8.0.26 and higher MySQL 8.0 versions. | Low |
| Group Replication | Amazon RDS doesn't support the MySQL Group Replication plugin. | Low |
| InnoDB tablespace encryption | Amazon RDS doesn't support the InnoDB tablespace encryption. | Low |
| InnoDB reserved word | InnoDB is a reserved word for Amazon RDS for MySQL. You can't use this name for a MySQL database. | Low |
| Keyring plugin | Amazon RDS doesn't support the MySQL keyring plugin. | Low |
| Password validation plugin | Amazon RDS doesn't support the MySQL `validate_password` plugin. | Low |
| Persisted system variables | Amazon RDS doesn't support MySQL persisted system variables. | Low |
| Restricted access | Amazon RDS restricts access to certain system procedures and tables that require advanced permissions. Also, Amazon RDS doesn't allow direct host access to a DB instance by using Telnet, Secure Shell (SSH), or Windows Remote Desktop Connection. | Low |
| Rewriter query rewrite plugin | Amazon RDS doesn't support the MySQL Rewriter query rewrite plugin. | Low |
| Semisynchronous replication | Amazon RDS doesn't support the MySQL semisynchronous replication. | Low |
| Transportable Tablespaces | Amazon RDS doesn't support the MySQL Transportable Tablespaces feature. | Low |
| X Plugin | Amazon RDS doesn't support the MySQL X Plugin. | Low |
The following table includes Oracle database features that Amazon RDS for Oracle doesn't support.
| Limitation | Description | Impact |
| --- | --- | --- |
| Active Data Guard | You can't use Active Data Guard with Oracle multitenant container databases (CDB). | Medium |
| Automatic Storage Management | Amazon RDS doesn't support Oracle Automatic Storage Management (Oracle ASM). | Medium |
| Database Activity Streams | Amazon RDS doesn't support Oracle Database Activity Streams for the single-tenant architecture. | High |
| File size limit | The maximum size of a single file on RDS for Oracle DB instances is 16 TiB. | Medium |
| FTP and SFTP | Amazon RDS doesn't support FTP and SFTP. | Medium |
| Hybrid partitioned tables | Amazon RDS doesn't support Oracle hybrid partitioned tables. | High |
| Oracle Data Guard | Amazon RDS doesn't Oracle Data Guard for the single-tenant architecture. | High |
| Oracle Database Vault | Amazon RDS doesn't support Oracle Database Vault. | High |
| Oracle DBA privileges Vault | Amazon RDS has limitations for Oracle DBA privileges. For more information, see [Limitations for Oracle DBA privileges](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Oracle.Concepts.limitations.html#Oracle.Concepts.dba-limitations). | High |
| Oracle Enterprise Manager | Amazon RDS doesn't Oracle Enterprise Manager for the single-tenant architecture. | High |
| Oracle Enterprise Manager Agent | Amazon RDS doesn't Oracle Enterprise Manager Agent for the single-tenant architecture. | Medium |
| Oracle Enterprise Manager Cloud Control Management Repository | You can't use an Amazon RDS for Oracle DB instance for Oracle Enterprise Manager Cloud Control Management Repository. | High |
| Oracle Flashback Database | Amazon RDS doesn't support the Oracle Flashback Database feature. | High |
| Oracle Label Security | Amazon RDS doesn't support Oracle Label Security for the single-tenant architecture. You can use Oracle Label Security only with multitenant container databases (Oracle CDB). | High |
| Oracle Messaging Gateway | Amazon RDS doesn't support Oracle Messaging Gateway. | High |
| Oracle Snapshot Standby databases | Amazon RDS doesn't support Oracle Snapshot Standby databases. | High |
| Public synonyms | Amazon RDS doesn't support public synonyms for Oracle-supplied schemas. | Medium |
| Schemas for unsupported features | Amazon RDS doesn't support schemas for Oracle features and components that require system privileges. | High |
| Pure unified auditing | Amazon RDS doesn't support the pure unified auditing. You can use the unified auditing in mixed mode. | Medium |
| Workspace Manager | Amazon RDS doesn't support the Oracle Database Workspace Manager `WMSYS` schema. | High |
The following table includes PostgreSQL database features that Amazon RDS for PostgreSQL doesn't support.
| Limitation | Description | Impact |
| --- | --- | --- |
| Concurrent connections | The maximum number of concurrent connections to your RDS for PostgreSQL instance is limited by the `max_connections` parameter. | Low |
| Newest versions | Amazon RDS doesn't apply major version upgrades automatically. To perform a major version upgrade, modify your DB instance manually. For more information, see [Choosing a major version upgrade for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.html#USER_UpgradeDBInstance.PostgreSQL.MajorVersion). | Low |
| Reserved connections | Amazon RDS reserves up to 3 connections for system maintenance. If you specify a value for the user connections parameter, add 3 to the number of connections that you expect to use. | Low |
| Supported extensions | RDS for PostgreSQL supports a limited number of extensions for the PostgreSQL database engine. You can find a list of supported extensions in the default DB parameter group for your PostgreSQL version. You can also see the current extensions list using `psql` by showing the `rds.extensions` parameter. | Low |
| Tablespace splitting or isolation | You can't use tablespaces for I/O splitting or isolation. In RDS for PostgreSQL, all storage is on a single logical volume. | Low |
The following table includes SQL Server database features that Amazon RDS for SQL Server doesn't support.
| Limitation | Description | Impact |
| --- | --- | --- |
| Backing up to Microsoft Azure Blob Storage | RDS for SQL Server doesn't support backing up to Microsoft Azure Blob Storage. | Medium |
| Buffer pool extension | RDS for SQL Server doesn't support the buffer pool extension. | High |
| Custom password policies | RDS for SQL Server doesn't support custom password policies. | Medium |
| Data Quality Services | RDS for SQL Server doesn't support SQL Server Data Quality Services (DQS). | High |
| Database Log Shipping | RDS for SQL Server doesn't support database Log Shipping. | High |
| Database names | Database names have the following limitations: can't start with rdsadmin; can't start or end with a space or a tab; can't contain any of the characters that create a new line; can't contain a single quotation mark ('). | Medium |
| Database snapshots | RDS for SQL Server doesn't support database snapshots. You can use only DB instance snapshots in Amazon RDS. | Medium |
| Extended stored procedures | RDS for SQL Server doesn't support extended stored procedures, including `xp_cmdshell`. | High |
| File tables | RDS for SQL Server doesn't support file tables. | Medium |
| FILESTREAM support | RDS for SQL Server doesn't provide FILESTREAM support. | Medium |
| Linked servers | RDS for SQL Server provides limited support for linked servers. | High |
| Machine Learning and R Services | RDS for SQL Server doesn't support Machine Learning and R Services because you need OS access to install these services. | High |
| Maintenance plans | RDS for SQL Server doesn't support maintenance plans. | High |
| Performance Data Collector | RDS for SQL Server doesn't support Performance Data Collector. | High |
| Policy-Based Management | RDS for SQL Server doesn't support Policy-Based Management. | Medium |
| PolyBase | RDS for SQL Server doesn't support PolyBase. | High |
| Replication | RDS for SQL Server doesn't support replication. | Medium |
| Resource Governor | RDS for SQL Server doesn't support Resource Governor. | High |
| Server-level triggers | RDS for SQL Server doesn't support server-level triggers. | Medium |
| Service Broker endpoints | RDS for SQL Server doesn't support Service Broker endpoints. | High |
| SSAS | Consider the limitations that apply to running SQL Server Analysis Services (SSAS) on RDS for SQL Server. For more information, see [Limitations](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Appendix.SQLServer.Options.SSAS.html#SSAS.Limitations). | Low |
| SSIS | Consider the limitations that apply to running SQL Server Integration Services (SSIS) on RDS for SQL Server. For more information, see [Limitations](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Appendix.SQLServer.Options.SSIS.html#SSIS.Limitations). | Low |
| SSRS | Consider the limitations that apply to running SQL Server Reporting Services (SSRS) on RDS for SQL Server. For more information, see [Limitations](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Appendix.SQLServer.Options.SSRS.html#SSRS.Limitations). | Low |
| Storage size for SQL Server DB instances | The maximum storage size for SQL Server General Purpose (SSD) storage and Provisioned IOPS storage instances is 16 TiB. The maximum storage size for SQL Server Magnetic storage instances is 1 TiB. | High |
| Stretch Database | RDS for SQL Server doesn't support the SQL Server Stretch Database feature. | Medium |
| T-SQL endpoints | RDS for SQL Server doesn't support all operations that use `CREATE ENDPOINT`. | High |
| TRUSTWORTHY database property | RDS for SQL Server doesn't support the `TRUSTWORTHY` database property because it requires the `sysadmin` role. | Medium |
The following table includes a list of recommendation issues. DMS Fleet Advisor analyses source and target database features and provides these migration limitations. The limitation with Blocker impact means that DMS Fleet Advisor can't generate target recommendations for the source database.
| Limitation | Description | Impact |
| --- | --- | --- |
| Appropriate instance is not found | AWS DMS can't find a target instance that can work as a right-sized migration destination for a combination of your source database metrics. | Blocker |
| Appropriate instance is not found by IOPS | The source database uses a number of IOPS, which exceeds the maximum number of IOPS for the possible target DB instances. | Blocker |
| Appropriate instance is not found by RAM | The source database uses a number of GB of RAM, which exceeds the maximum size of RAM for the possible target DB instances. | Blocker |
| Appropriate instance is not found by storage size | The source database uses a number of TB of storage, which exceeds the maximum storage size for the possible target DB instances. | Blocker |
| Appropriate instance is not found by edition | The source database has an edition, which is not supported by Amazon RDS. | Blocker |
| Appropriate instance is not found by CPU cores | The source database has a number of CPU cores, which exceeds the maximum number of CPU cores for the possible target DB instances. | Blocker |
| Appropriate instance is not found by version | Your source database has version, which AWS DMS doesn’t recognize. | Blocker |
| CPU parameter is undefined | The DMS data collector didn't collect information about the CPU that your source database uses. Make sure that you collected the required metrics and configured credentials for data forwarding in your data collector. See [Configuring credentials for data forwarding](fa-data-collectors-install.md#fa-data-collectors-configure). | Blocker |
| Memory parameter is undefined | The DMS data collector didn't collect information about the memory that your source database uses. Make sure that you collected the required metrics and configured credentials for data forwarding in your data collector. See [Configuring credentials for data forwarding](fa-data-collectors-install.md#fa-data-collectors-configure). | Blocker |
| Storage size parameter is undefined | The DMS data collector didn't collect information about the storage size that your source database uses. Make sure that you collected the required metrics and configured credentials for data forwarding in your data collector. See [Configuring credentials for data forwarding](fa-data-collectors-install.md#fa-data-collectors-configure). | Blocker |
| Storage IOPS parameter is undefined | The DMS data collector didn't collect the storage IOPS metrics for your source database uses. Make sure that you collected the required metrics and configured credentials for data forwarding in your data collector. | Blocker |
| Not Enough Data | The DMS data collector didn't collect enough data to generate a target recommendation. Make sure that you configured credentials for data forwarding in your data collector. See [Configuring credentials for data forwarding](fa-data-collectors-install.md#fa-data-collectors-configure). | Blocker |
| Database edition is undefined | The DMS data collector didn't collect information about your source database edition. Make sure that you collected the required metrics and configured credentials for data forwarding in your data collector. See [Configuring credentials for data forwarding](fa-data-collectors-install.md#fa-data-collectors-configure). | Blocker |
| Unknown Error | DMS Fleet Advisor can't generate target recommendations for your source database. | Blocker |
| Database version is undefined | The DMS Fleet Advisor didn't collect information about your source database version. DMS Fleet Advisor recommends that you use the latest database version for your source database. If you choose this recommendation, then you must upgrade your database version. Review the generated target recommendations for your source database and make sure that these recommendations meet your requirements. | High |
| Increase the number of database connections in RDS settings | Your source database requires certain number of connections. By default, the number of available connections for Amazon RDS database instances is different. Make sure that you change this default value when you create your RDS database instance. To do so, update the max\$1connections parameter value in Parameter Groups. | Medium |
| Target edition is compatible | The target recommendation for your source database uses a different database edition. Your source database edition supports the same features as the recommended target edition. However, choosing this new database edition might increase your expenses. | Medium |
| Storage throughput parameter is undefined | The DMS data collector didn't collect the storage throughput metrics for your source database uses. Review the generated target recommendations for your source database and make sure that these recommendations meet your requirements. | Medium |
| Database connection number parameter is undefined | The DMS data collector didn't collect information about the number of connections that your source database uses. Review the generated target recommendations for your source database and make sure that these recommendations meet your requirements. Alternatively, request a quota increase. | Medium |
| Database downgrade version | Your source database runs on a higher version than the Amazon RDS database. To downgrade your database version, make sure that you don't use the features that aren't implemented in lower version. Alternatively, use Amazon EC2 as a migration target. | Medium |
| Target edition is different | The target recommendation for your source database uses a different database edition. Your source database edition is compatible with the recommended target edition. However, the recommended target database edition doesn't support some features of your source database edition. Choosing this new database edition might increase your expenses. | Medium |
| Upgrade from an unsupported version | Your source database has reached the end of support stage. To use the latest DB engine version as a target, upgrade your database before the migration. Alternatively, use Amazon EC2 as a migration target.Depending on the database engine, use one of the following links for Learn more:[Upgrading MySQL](https://dev.mysql.com/doc/refman/8.0/en/upgrading.html)[Upgrade SQL Server](https://learn.microsoft.com/en-us/sql/database-engine/install-windows/upgrade-sql-server?view=sql-server-ver16)[Upgrade OracleDB](https://docs.oracle.com/en/database/oracle/oracle-database/19/upgrd/index.html)[Upgrade PostgreSQL](https://www.postgresql.org/docs/15/upgrading.html) | Medium |
# Troubleshooting for target recommendations with AWS DMS Fleet Advisor
**Important**
End of support notice: On May 20, 2026, AWS will end support for AWS Database Migration Service Fleet Advisor. After May 20, 2026, you will no longer be able to access the AWS DMS Fleet Advisor console or AWS DMS Fleet Advisor resources. For more information, see [AWS DMS Fleet Advisor end of support](https://docs.aws.amazon.com/dms/latest/userguide/dms_fleet.advisor-end-of-support.html).
In the following list, you can find actions to take when you encounter issues with the DMS Fleet Advisor Target Recommendations feature.
**Topics**
+ [I can't see price estimates for target recommendations](#fa-recommendations-troubleshooting-price-estimates)
+ [I can't see resource utilization charts](#fa-recommendations-troubleshooting-charts)
+ [I can't see the metrics collection status](#fa-recommendations-troubleshooting-metrics)
## I can't see price estimates for target recommendations
If you see the **No data** for the **Estimated monthly cost** for a recommendation with a status of **Success**, then make sure that you granted your IAM user with permissions to access the AWS Price List Service API. To do so, you must create the policy that includes the `pricing:GetProducts` permission and add it to your IAM user as described in [Create IAM resources](fa-resources.md#fa-resources-iam).
DMS Fleet Advisor doesn't calculate the estimated monthly cost for recommendations with a status of **Failed**.
## I can't see resource utilization charts
If you see the **Failed to load metrics** message after you expand the **Source utilization and capacity** section, then make sure that you granted your IAM user with permissions to view Amazon CloudWatch dashboards. To do so, you must add the required policy to your IAM user as described in [Create IAM resources](fa-resources.md#fa-resources-iam).
Alternatively, you can create a custom policy which includes the `cloudwatch:GetDashboard`, `cloudwatch:ListDashboards`, `cloudwatch:PutDashboard`, and `cloudwatch:DeleteDashboards` permissions. For more information, see [Using Amazon CloudWatch dashboards](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch_Dashboards.html) in the *Amazon CloudWatch User Guide*.
## I can't see the metrics collection status
If you see the **No data available** for **Metrics collection** when you choose **Generate recommendations**, then make sure that you collected data. For more information, see [Collecting data for AWS DMS Fleet Advisor](fa-collecting.md).
If you have this issue after you collected data, then make sure that you granted your IAM user with the `cloudwatch:Get*` permission to access Amazon CloudWatch. DMS Fleet Advisor uses a service-linked role to publish the collected database performance metrics to CloudWatch on your behalf. Make sure to create a service-linked role to use with DMS Fleet Advisor. For more information, see [Create IAM resources](fa-resources.md#fa-resources-iam).