AWS Database Migration Service (DMS) task is where we configure the databases and collections we want to migrate.
You specify which collections (
tables) and database (
schemas) to be migrated, and any additional processing, such as logging requirements, control table data, and error handling.
At the AWS DMS console–>Database migration tasks screen, click on Create task.
Create database migration task:
Migrate existing data and replicate ongoing changes. Here you can choose between three methods: -
full load(Migrate existing data), -
CDC only(Replicate data changes only) and -
full load + CDC(Migrate existing data and replicate ongoing changes)
Do nothing- so we preserve the indexes already created and collections metadata.
Limited LOB mode
Leave log levels at the defaults.
Table mappings -> Add new selection rule
labdb schema which is our database to migrate
%- it means all collections from the selected
Premigration assessment unchecked.
Migration task startup configuration:
Automatically on create
Do not change
Advanced task settings.
Do not need to include
Click on Create task.
In a minute or so, your task Identifier status will change from Creating, to Ready and then Starting.
After another minute you should see your task running in state Load complete, replication ongoing.
If your task did not start and shows a Ready status, you may Start it manually.
Click on your migration task Identifier
Then go to Table statistics tab to check the progress of data migration.
Click on the refresh button to update until you see the Load State as Table completed. Then you will start to see new records inserted from time to time coming from the Lambda function.
Full load record count may vary from hundreds to thousands of records, depending on how long the Lambda ingestion application has been running.
The Load state Table completed means that the full load is over and incremental changes will now be replicated .