In AWS DMS for SQL Server is there a way to specify the setting logScanBatchSize

When DMS reads from a SQL Server TRN file ( maybe starting in 3.5.3 ) it uses the function called fn_dump_dblog() to read .TRN backups from the database server.

By default the software utilized by DMS does not limit the records pulled or might have a default of 50000

logScanBatchSize might be available to say select top 1000 and allow the system to run. I don't see performance issues on SQL, but it does appear to cause latency on DMS when the TRN file is large ( 10 gigs )

select /* top 50000 */
	[Current LSN],
	[operation],
	[Context],
	[Transaction ID],
	[Transaction Name],
	[Begin Time],
	[End Time],
	[Flag Bits],
	[PartitionID],
	[Page ID],
	[Slot ID],
	[RowLog Contents 0],
	[Log Record],
	[RowLog Contents 1] -- After Image
from sys.fn_dump_dblog (NULL, NULL,NULL, 1,'C:\Backup\backup.TRN'...

Existing code looks like above. The 50000 is commented out probably indicating its being set behind the scenes to 0 or -1, not sure.

Is there a way we can control this to see if top 1000 etc makes a difference? I know sometimes the TRN may have large quantities of unrelated transactional records that might be involved.

When using dbcc outpbuffer(spid) I notice that it appears to only be grabbing a few records every minute or so leading to high CDC source latency and consequentially high target latency. Even when DB activity was relatively light(few thousand records an hour ).

Any help would be appreciated.

Thank you