You can use several different techniques to import data into an RDS for MariaDB DB instance. The best approach depends on a number of factors:
Source of the data
Amount of data
One-time import or ongoing
Amount of downtime
If you are also migrating an application with the data, the amount of downtime is important to consider.
The following table lists techniques to importing data into an RDS for MariaDB DB instance:
NoteAmazon RDS only supports importing from Amazon S3 into RDS for MySQL DB instances. Importing backups created with mariadb-backup into RDS for MariaDB isn't currently supported.
The mysql system database contains authentication and authorization information required to log in to your DB instance and access your data. Dropping, altering, renaming, or truncating tables, data, or other contents of the mysql database in your DB instance can result in errors and might render the DB instance and your data inaccessible. If this occurs, you can restore the DB instance from a snapshot using the AWS CLI restore-db-instance-from-db-snapshot command. You can recover the DB instance using restore-db-instance-to-point-in-time command.
Upgrade options for unsupported engine versions
Importing data considerations
Did this page help you? - Yes
Thanks for letting us know we're doing a good job!
If you've got a moment, please tell us what we did right so we can do more of it.
Did this page help you? - No
Thanks for letting us know this page needs work. We're sorry we let you down.
If you've got a moment, please tell us how we can make the documentation better.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4