Thank you for the note. May I ask - Why didn't you move to a Graviton2 instance by upgrading the primary or the reader instance? The downtime with this approach is just 60-120 seconds. We always suggest using native tools rather than AWS DMS for homogeneous migrations.
A key gap here is that the UI does not indicate that the instance types have been filtered based on the Aurora version. I would lose 10 inserts per second during any downtime. So the only option I could see was to use DMS. I spent about 6 hours battling DMS because the DMS info omitted to mention the requirement to restart the cluster after changing the parameter group to allow replication. I only found this detail by chance on a parameter group doc page.
Migrating catalog table to Aurora Mysql targetasked 2 years ago
Migrating from RDS MariaDB 10.2 to Aurora MySQL 5.6Accepted Answerasked 4 years ago
Best practices for migrating MySQL RDS to Aurora ServerlessAccepted Answerasked 4 years ago
DMS migration from Aurora MySQL 5.6 to Aurora MySQL 5.7 on gravitonasked 2 months ago
Migrate MySQL 8 to Aurora MySQL 8asked 9 months ago
Aurora Serverless MySQL to access the binlog or Activity Streamsasked a year ago
Delayed Replication w/ Aurora MySQLAccepted Answerasked 4 years ago
Migrating from MySQL to Aurora (Using Replica)asked 2 years ago
Are there difficulties migrating from Aurora MySQL to Aurora ServerlessAccepted AnswerMODERATORasked 2 years ago
Migrate RDS MySQL 8.0.28 to Aurora MySQLasked 4 months ago