Using DMS to Configure Ongoing Replication from RDS to Redshift

30 minutes
  • 3 Learning Objectives

About this Hands-on Lab

In this lab, you will set up a replication instance, configure an existing RDS instance as a source endpoint, define Redshift as a target endpoint, and configure a Database Migration Task to replicate existing data with ongoing replication from our RDS source to the Redshift target.

Learning Objectives

Successfully complete this lab by achieving the following learning objectives:

Configure the DMS Replication Instance
  1. Navigate to the DMS dashboard.
  2. Click Replication instances.
  3. Click Create replication instance.
  4. Create the DMS replication instance with the following:
    • Name: wild-llama-dms
    • Instance class: dms.t3.micro
    • Engine verison: 3.4.6
    • Allocated storage: 50 gb
    • Choose VPC: acgdmslab
    • Uncheck Publicly Accessible
  5. Under Advanced settings, select a security group (acgDMSLabSG).
  6. Click Create.

    Note: If you get a message that the IAM role is not configured properly, wait a moment, and then click Create again.

Configure Source and Target Endpoints
  1. Navigate to the DMS dashboard.
  2. Click Endpoints.
  3. Click Create endpoint.

Source Configuration:

  • Choose the Source endpoint type.
  • Select the RDS instance checkbox.
  • Change Access to endpoint database to Provide access information manually.
  • Enter the password for the lab, leave everything else as is.
  • Under Test endpoint connection (optional), chooose the VPC acgdmslab, select the replication instance created earlier in the lab, and click Run test.
  • Once the status returns as successful, click Create endpoint.

Target Configuration:

  • Choose the Target endpoint type.
  • Add an Endpoint identifier of "wlt-redshift".
  • Change the Target engine to Amazon Redshift.
  • Change Access to endpoint database to Provide access information manually.
  • Enter the server name for Redshift.
  • Enter 5439 for the port.
  • Enter "cloud_user" for the User name.
  • Enter the password for Redshift (found in your lab credentials) in the Password field.
  • Enter a Database name of "wild_llama_travel".
  • Under Test endpoint connection (optional), chooose the VPC acgdmslab, select the replication instance created earlier in the lab, and click Run test.
  • Once status returns as successful, click Create endpoint.
Configure Replication Task
  1. Navigate to the DMS dashboard.
  2. Click Database Migration Tasks.
  3. Click Create Task:
    • Enter a Task identifier of "wlt-rds-to-redshift".
    • Choose the Replication instance named wild-llama-dms we created in Objective 1.
    • Choose the RDS Source and Redshift Target in the dropdowns that match what we created in Objective 2.
    • Choose Migration type of Migrate existing data and replicate ongoing changes.
    • Leave task settings at their defaults.
    • Under Table mappings, choose Add new selection rule.
    • Under the Schema dropdown, choose Enter a schema.
    • Enter a schema name of "wild_llama_travel".
    • Leave Table name as %.
    • Set Action to Include.
    • Leave Migration task to automatically start on create.
    • Click Create task.

Additional Resources

Scenario

As a database administrator for Wild Llama Travel, your team has created an AWS Redshift data warehouse and would like you to migrate existing data and replicate ongoing changes from your production MySQL database, which currently exists as an AWS RDS instance. To facilitate this, you will be using AWS Database Migration Service and performing the following objectives:

  • Creating a replication instance. (Note: Use replication engine version 3.4.6.)
  • Defining the preexisting RDS instance as a source.
  • Defining the Redshift data warehouse as the target.
  • Creating a DMS task to migrate the existing data and replicate ongoing changes.

Your lab contains a preconfigured RDS instance, loaded with several database tables as well as a Redshift instance. To begin the lab, please log in to the AWS console using the provided link and credentials in the lab.

What are Hands-on Labs

Hands-on Labs are real environments created by industry experts to help you learn. These environments help you gain knowledge and experience, practice without compromising your system, test without risk, destroy without fear, and let you learn from your mistakes. Hands-on Labs: practice your skills before delivering in the real world.

Sign In
Welcome Back!

Psst…this one if you’ve been moved to ACG!

Get Started
Who’s going to be learning?