Amazon DMS Serverless limitations - Amazon Database Migration Service
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Amazon DMS Serverless limitations

Amazon DMS Serverless has the following limitations:

  • You can only modify an Amazon DMS replication configuration that is in the CREATED, STOPPED, or FAILED states. For details about which settings you can change under which conditions, see Modifying Amazon DMS serverless replications.

  • You can only delete an Amazon DMS replication configuration that is in the STOPPED, or FAILED states.

  • Unlike replication instances, Amazon DMS Serverless replications do not have a public IP address for management tasks. You manage serverless replications using the console.

  • This release of Amazon DMS serverless does not support all the source and target endpoint types that Amazon DMS standard supports. For a list of supported engine types, see Amazon DMS Serverless components.

  • Serverless replications need to access dependencies by using VPC endpoints. You must use VPC endpoints to access the following endpoint types:

    • Amazon Amazon S3

    • Amazon Kinesis

    • Amazon Secrets Manager

    • Amazon DynamoDB

    • Amazon Redshift

    • Amazon OpenSearch Service

    For information about setting up VPC endpoints, see Configuring VPC endpoints as Amazon DMS source and target endpoints.

  • Amazon DMS serverless does not support views.

  • Amazon DMS Serverless does not support SSL connections for DB2 endpoints.

  • Amazon DMS Serverless does not support setting custom CDC start points.

  • When a replication task is in deprovisioned state, the metadata related to the table and the replication statistics are lost.