- Newest
- Most votes
- Most comments
Hi Hanmari.
I would recommend you checking AWS Database Migration Service (DMS). It can accomplish exactly what you are looking for.
Essentially you would connect both source and destination databases using endpoints and create a migration task in a DMS instance. You can even establish to maintain the destination database automatically up to date. There is also the option to use DMS Serverless which eliminates the need for you to manage another instance.
I hope this helps.
You can create a read replica of your RDS instance for the reporting server.
I already have my main database replicated and am trying to avoid having to read from its replicas. The queries I am running on my logging database take a long time to run and the replicated servers time out the connection. I have tried increasing the timeout delay to ninety seconds, but this has not worked and I do not wish to push this restraint further. Foreign Data Wrapper connections have similarly failed to yield a stable, long-lasting connection for my number-crunching reports.
Relevant content
- asked a year ago
- asked 2 years ago
AWS OFFICIALUpdated 2 years ago- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
Hi there. If this answer helped, please consider accepting it. Thank you!
Hi Jose, I am looking into the data migration service angle. I was under the impression that data migration services were intended for a single-use export of a large dataset. My use case is very small and needs to reoccur regularly. So far, I have not seen any tools to implement a recurring copy/replace process. I imagine I would need to save the migration as a process that I could execute from the AWS CLI and then use a cron to trigger the migration on a schedule. The DMS Serverless option sounds promising if I can figure out the over-engineered interface.