Skip to main content

Using AWS Data Migration Service

 Want to share this easily? 

Check out the Notion page.

By Morgan Lucas (she/her) from this video by Johnny Chivers

We use data migration services to, well, migrate data. But why would we want to do this?


  • We're moving our business to the cloud, and need to shift all of that cold storage we have onsite.
  • We want to use it as a backup in cause our infrastructure is out of commission.
  • We could have information to share with a 3rd party, and instead of giving access to on-site databases, we put it on AWS to share.
Nevertheless, let's recap what I've done.
  • Created publicly accessible, password-protected database with Amazon Aurora with PostgreSQL Compatibility to migrate to Amazon Dynamo DB
  • Managed inbound rules of security group to limit access
  • Used open source software HeidiDB to interact with database via a TCP/IP session and specific URL for DB (Not shown here for security)



  • Connected to Aurora PostgreSQL Database
    • ran queries that deleted and created tables populated with new information
  • Created publicly accessible replication instance to connect to our RDS to initiate database migration
  • Created configuration endpoints with existing instance used to migrate database User_Data to Amazon DynamoDB
  • Created role to talk to DMS (making sure to click the radio button beneath)
  • Successfully connected target (endpoint) to instance (middleman to transfer data)
  • Set up database migration task to move from Aurora PostgreSQL Database to Amazon DynamoDB

Find me on Twitter, or my blog. You can Buy Me A Coffee and help me keep writing!


Popular posts from this blog

Connecting IoT Devices to a Registration Server (Packet Tracer, Cisco)

In Packet Tracer, a demo software made by Cisco Systems. It certainly has changed a lot since 2016. It's almost an Olympic feat to even get started with it now, but it does look snazzy. This is for the new CCNA, that integrates, among other things, IoT and Automation, which I've worked on here before. Instructions here . I don't know if this is an aspect of "Let's make sure people are paying attention and not simply following blindly", or an oversight - The instructions indicate a Meraki Server, when a regular one is the working option here. I have to enable the IoT service on this server. Also, we assign the server an IPv4 address from a DHCP pool instead of giving it a static one. For something that handles our IoT business, perhaps that's safer; Getting a new IPv4 address every week or so is a minimal step against an intruder, but it is a step. There are no devices associated with this new server; In an earlier lab (not shown), I attached them to 'H

Building, Breaking, and Building A CRM with Retool

 I like no- or low-code solutions to things. I've often wanted to simply push a button or move some GUI around and have the code implement itself.  I've thought about building something that's like a customer relationship management (CRM) system for keeping up with my network better than my little spreadsheet where I click links and then go like something. The general idea in this CRM Development is:  To have a GUI to add people to a NRM (Network Relationship Management).       Attach it to a database (MySQL is what I went with eventually using Amazon Relational Database service, but you can use PostGRES, and probably others).     Make sure components are connected to each other in the retool interface. This video is a good start. Watching the tutorial video, heard some SQL commands and went 'Oh no 😳" before going "Wait I know basic SQL", which is good, because you'll see.  When you get set up, there's a plethora of resources you can use -- Incl

What Do You Need? [List of Offered Services]

2023 Version is here, at this handy Notion Page.