Does AWS DMS load full binlog from source regardless if you only need a table or two?

Hello,

Per the documentation, a full binlog is required when using MySQL as a source. DMS will filter based on which databases and tables you are replicating.

Documentation here: https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Source.MySQL.html#CHAP_Source.MySQL.CustomerManaged

based on the number of tables involved dms will query the binlog (log mining) for ddl/dml changes and wont get full binlog to dms instance.

There's no separation of tables in the binlog. All transactions / datapages for all tables (and objects) are kept there in serialized mode. Maybe in the future it could happen, given the source is open to handle this. This is done this way for consistency enforcement (transaction serialization) with rollback in mind either. Its very possible today to restore a database in a separate server, and then do the import on the required server Another alternative is to export the snapshot to s3 for the specific table. Check this out https://dplab.medium.com/restore-specific-table-data-from-rds-backup-eb3623786f5e