Create and monitor the tasks

An AWS Database Migration Service (AWS DMS) task is where all the work happens. You specify what tables (or views) and schemas to use for your migration and any special processing, such as logging requirements, control table data, and error handling.

When creating a migration task, you need to know several things:

  • Before you can create a task, you must create a source endpoint, a target endpoint, and a replication instance.
  • You can specify many task settings to tailor your migration task. You can set these by using the AWS Management Console, AWS Command Line Interface (AWS CLI), or AWS DMS API. These settings include specifying how migration errors are handled, error logging, and control table information.
  • After you create a task, you can run it immediately. The target tables with the necessary metadata definitions are automatically created and loaded, and you can specify ongoing replication.
  • By default, AWS DMS starts your task as soon as you create it. However, in some situations, you might want to postpone the start of the task. For example, when using the AWS CLI, you might have a process that creates a task and a different process that starts the task based on some triggering event. As needed, you can postpone your task’s start.
  • You can monitor, stop, or restart tasks using the AWS DMS console, AWS CLI, or AWS DMS API.

In this section you will:

  • Create a total of 4 migration tasks:
    • 1 for MySQL (wordpressdb)
    • 3 for PostgreSQL (ofbiz, ofbizolap and ofbiztenant)