This is an AWS DMS issue.
DMS has recently added a feature WAL heartbeat  (run dummy queries) for replication from a PostgreSQL source so idle logical replication slots do not hold on to old WAL logs which may result in storage full situations on the source. This heartbeat keeps restart_lsn moving and prevents storage full scenarios.
- Login to DMS Console.
- Stop all the tasks related to the source endpoint
- Click on "Endpoints" from left side selection pane.
- Select the source Endpoint which you are using, as per the task.
- Click on "Modify" from the top of the screen.
- Expand "Advanced".
Under extra connection attribute, please add this:
HeartbeatEnable – set to true (default is false)
HeartbeatSchema – schema for heartbeat artifacts (default is public)
HeartbeatFrequency – heartbeat frequency in minutes (default is 5 and the minimum value is 1)
- Click on "Modify". You will be automatically redirected to the Endpoints screen.
- Select the endpoint again and click on "Test Connection".
- It should automatically start the testing. Wait for it to show "Successful".
Stopping the task alone will not clear replication slot, so the storage usage will still increase when the task is in the stopped state, you will need to delete task to clear the slot.
To clear up the replication slots use the following commands -
SELECT * FROM pg_replication_slots ; --finds all replication slots
select pg_drop_replication_slot('NameOfSlot'); -- you will get the name of the slot from the first command
 PostgreSQL Source WAL Heartbeat