I created a snapshot of my RDS Postgres DB, and I am trying to use that snapshot to create an AWS Aurora DB using the migrate snapshot option in AWS console, however the option is disabled for me, and I can't understand why?
According to this official AWS blog, I should be able to migrate my RDS postgres DB into Aurora DB using the migrate snapshot option.
I created this snapshot from a Postgres DB running on version 12.5. I have created another snapshot from another Postgres DB running on version 9.6.20, and I face the same issue there as well.
12.5 and 9.6.20 versions of PostgresSQL are not supperted by aurora. What is supported is listed here.
Related
We are planning to migrate a RDS PostgreSQL database to aurora. First I made a snapshot, but the migration option is grayed out. Our PostgreSQL version is 11.13. From the AWS documentation it mentioned that: 'starting with the release of PostgreSQL versions 13.3, 12.8, 11.13, 10.18, and for all other later versions, Aurora version numbers aren't used.', I do not understand what does this means. Is this a version problem? Please advise what should I do. Thanks
I have PostgreSQL DB running on Version 10.15 for which I like to created an Aurora Read Replica as mentioned in this official document, however in the AWS console I only have the option of Create Read Replica only and not Create Aurora Read Replica. The option is completely missing.
If I choose to Create Read Replica, it then just create another PostgreSQL instance instead of Aurora PostGres, and that's is not what I want.
P.s: I have auto back-up enabled for that instance
You must be running RDS PostegreSQL, as there is no Aurora PostegreSQL 10.15.
For the RDS, you only create read replicas as indicated in the AWS Console. Aurora replicas are only for Aurora PostgreSQL (not RDS PostgreSQL).
If I understood it correct, you have an RDS PostgreSQL instance (not Aurora) and want to create an Aurora PostgreSQL Read Replica from it. With steps mention on documentation link you shared.
This is possible and I could reproduce it, but not for all version.
I tested with MySQL, not with PostgreSQL, but the mechanism is the same.
I created one RDS MySQL (not Aurora) version 5.7.33 and from this one I can create Aurora Read Replica, as you can see from picture below.
The other one I created RDS MySQL (not Aurora) version 8.0.23, this one doesn't show me the option to create Aurora Read Replica.
Update
The rules to have this option enable is:
The same major version between RDS and Aurora
Minor version equal or higher on Aurora.
With versions we have today on RDS PostgreSQL and Aurora PostgreSQL, none match the rules above.
But we have a match for MySQL, as I showed.
If you want to migrate from RDS to Aurora, even though this options is not available you have other options, like snapshot and DMS.
With regards to Aurora MySQL,
Aurora MySQL 2. x versions are compatible with MySQL 5.7 and
Aurora MySQL 1. x versions are compatible with MySQL 5.6.
When creating a new Aurora MySQL DB cluster (including restoring a snapshot), you have the option of choosing compatibility with either MySQL 5.7 or MySQL 5.6.
This implies that When creating the RDS for MySQL instance, you are limited to versions of MySQL 5.6 or 5.7 (if you intend to create Aurora MySQL read replicas)
https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.2044.html
I want to periodically sync my Cloud SQL Postgres DB with an Amazon Aurora DB.
Setting up a Lambda that does pgdump and psql from one to the other should work but is there a cleaner solution?
You can take a look at the Database Migration Service in AWS. As long as one of the databases is in AWS (which Aurora is) you can use it to perform full-loads + continuous migration using Change Data Capture. PostgreSQL is supported, so you'd have to create a migration instance, configure the Postgres and Aurora endpoints and set up a replication task.
Reference
Creating tasks for ongoing replication using AWS DMS
I ended up running a pg_dump and psql cron job on an EC2 instance. I could not access GCP db as endpoint as from DMS for some reason.
We need to replicate data from an Amazon RDS (MySQL) databaes to an Aurora PostgreSQL database. Each database is on a different AWS account and region.
The data must be replicated in the PostgreSQL instance every 6 hours, so we need the guarantee that the data doesn't duplicate even if a field updated for a record.
Which method, tool, or design is better to do that? (Could be different to AWS.)
You could facilitate one of the following services provided by AWS:
Database Migration Service
Glue
The AWS Database Migration Service supports:
Using an Amazon-Managed MySQL-Compatible Database as a Source for AWS DMS
Using a PostgreSQL Database as a Target for AWS Database Migration Service
I can't seem to find much information about the "migrate snapshot" option in the AWS/RDS documentation.
Is it correct to assume that it creates a new, totally separate database based on that snapshot and leaves the original database intact?
The Migrate Snapshot function spins up a new Aurora DB Cluster from a MySQL DB snapshot.
The Migrate Snapshot button in AWS Web Console is currently active only for MySQL snapshots. Naming and appearance of the button is unfortunate. It would probably be more intuitive to only show that button for when a MySQL snapshot is selected and name it as Restore to Aurora or Launch Aurora Cluster.
You can find more information about that function in the AWS RDS user guide under Migrating an RDS MySQL Snapshot to Aurora subsection of the Aurora on Amazon RDS section.
Yes, if you spin up an instance from an RDS snapshot, it creates a completely new instance and leaves the original intact.