Wondering how to migrate to an Amazon RDS instance using AWS DMS? We can help you.

Here, at Bobcares, we assist our customers with several AWS queries as part of our AWS Support Services.

Today, let us see how our Support Techs assist with this AWS query.

How to migrate to an Amazon RDS instance using AWS DMS?

Today, let us see the steps followed by our Support techs in migration.

Create a replication instance

Create target and source endpoints

• Open the AWS DMS console, and choose Endpoints from the navigation pane.
• Choose Create endpoint to create the source and target database.
• For Endpoint type, choose Source.
• Enter the endpoint’s engine-specific information, such as the server name, port, SSL mode, or the Amazon Simple Storage Service (Amazon S3) bucket name, if you use Amazon S3 as the source.
• Then, choose Run Test.
• After the test is complete, choose Save.
• Repeat steps 3-6, but for Endpoint type, choose Target.

Refresh the source endpoint schemas

• Open the AWS DMS console, and choose Endpoints from the navigation pane.
• Select the source endpoint, and choose Refresh schemas.
• Finally, choose Refresh schemas.

Create a migration task

• Open the AWS DMS console, and choose Database migration tasks from the navigation pane.
• Then, choose Create task.
• Specify the Task identifier, Replication instance, Source database endpoint, Target database endpoint, and Migration type. Choose one of the following migration types:
  Migrate existing data only—Use this migration type for one-time migrations.
  Migrate existing data and replicate ongoing changes—Use this migration type to migrate large databases to the AWS Cloud with minimal downtime.
  And migrate ongoing replication changes—Use this migration type when you have already migrated the existing data and want to synchronize the source database with the target MySQL database hosted on the AWS Cloud.
• From the Task Settings section, modify the task as needed.
• Then, from the Table mappings section, choose Guided UI.
• Next, choose Add new selection rule, and specify your Schema and Table name.
• Choose Create task.

Monitor your migration task

Migrating Oracle

When using Oracle as the source database, the tables are migrated to the specified target endpoint user.

You can change the schema for an Oracle target by using transformation rules.Migrating MySQL

When migrating from MySQL to Amazon Aurora, use engine native tools when possible.

During migration, schemas and tables are migrated to the same name on the target.

If you want to migrate tables to a different schema on target, create a mapping rule to specify the new schema on the target database:

{
"rules": [{
"rule-type": "selection",
"rule-id": "1",
"rule-name": "1",
"object-locator": {
"schema-name": "test",
"table-name": "%"
},
"rule-action": "include"
}, {
"rule-type": "transformation",
"rule-id": "2",
"rule-name": "2",
"rule-action": "rename",
"rule-target": "schema",
"object-locator": {
"schema-name": "test"
},
"value": "newtest"
}
]
}

Check the logs to confirm that there are no errors.

Monitor latency and compare data counts on the source and the target databases before switching to the new target database.

[Need help with the process? We’d be happy to assist you]

Conclusion

To conclude, here we saw how our Support Techs migrate to an Amazon RDS instance using AWS DMS.