Serverless aurora v1 5.7 mysql migration to provisioned aurora mysql 5.7 using DMS with migrate type Full load, ongoing replication is not working

1. Aurora Serverless v1 does not support binary log replication, which is required for your DMS migration. You will need to convert your Aurora Serverless v1 cluster to a provisioned cluster.

2. The conversion process from Aurora Serverless v1 to provisioned will involve a short downtime, typically around 2 minutes, as Aurora performs a switchover from the reader to the writer instance. It's recommended to perform this conversion during a period of low activity, as long-running transactions can lengthen the switchover process.

3. To perform the conversion, you can use the AWS CLI with the following command:

aws rds modify-db-cluster \
    --db-cluster-identifier sample-cluster \
    --engine-mode provisioned \
    --allow-engine-mode-change \
    --db-cluster-instance-class db.r5.xlarge

This will not change your current endpoint URL.

4. Once your cluster is provisioned, you can then upgrade from Aurora MySQL 5.7 to Aurora MySQL 8.0, and then upgrade to Aurora Serverless v2. This process will involve longer downtime, and you can mitigate it by performing a Blue/Green deployment, as outlined in the documentation: https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments-overview.html

5. The provisioned Aurora MySQL 5.7 instance does support binary log replication, which means you can use DMS to replicate the data from the provisioned instance to an Aurora Serverless v2 cluster.

6. Alternatively, you can also consider the Blue/Green deployment approach to migrate directly from the provisioned Aurora MySQL 8.0 instance to an Aurora Serverless v2 cluster, as described in the documentation: https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-serverless-v2-administration.html#aurora-serverless-v2-converting-from-provisioned

I hope the above information is helpful!