Change Aurora Serverless engine version/family in AWS console - amazon-web-services

Where can I change the Aurora Serverless engine version/family through the AWS web console?
If I click Modify on the database page I don't see any setting (but that's where it is for non-Serverless databases), nor do I see a setting in Parameter Groups.

Sadly, you can't change it directly. For the aurora serverless you can only modify:
Minimum Aurora capacity unit
Maximum Aurora capacity unit
Timeout action
Pause after inactivity
If you want to change version of Aurora Serverless (for example from MySQL 5.6 to 5.7), you can snapshot your Aurora Serverless DB, and the restore to new Serverless MySQL to new version. This will allow you to change MySQL version, but not from MySQL to PostgreSQL. For that probably need to use AWS DMS.

Related

How can I use the Query Editor for Amazon Aurora v2?

Currently, I have created an Aurora Serverless v2 MySQL database cluster.
When it comes to using the Query editor I get the following message:
No databases that support query editor
Currently, query editor only supports Aurora Serverless databases. Only Aurora Serverless database that you have access to will be displayed.
To use the query editor for a database, the database must have the Data API enabled.
The Data API option in the Additional Connectivity section isn't available anymore and I couldn't find it so I skipped it.
As per docs:
The Data API and query editor aren't supported for Aurora Serverless v2.
The query editor is available only for Aurora Serverless v1 DB clusters using specific Aurora MySQL and Aurora PostgreSQL versions that support the Data API.

RDS - Aurora Serverless - is that possible to Migrate from Aurora Serverless to Aurora Provisioned?

Say I am running Aurora serverless cluster(MySql). If in case I need to go back to Aurora Provisioned (MySql), is this possible to migrate?
This is clear cut approach mentioned here
Modify writer instance by selecting and choosing modify instance configuration to anything other than serverless

Upgrading from AWS Aurora Serverless v1 to v2 fails

So with Aurora Serverless v2 available we wanted to upgrade from our Postgres Serverless v1.
The steps described are basically to take a snapshot, create a new Provisioned Aurora cluster (not Serverless) and then upgrade the Provisioned Cluster to Postgres 13.6 and after that Clone the new 13.6 Cluster into a Serverless v2.
However, I get stuck on the last part as when trying to clone it I get "Serverless (incompatible minor version)" and the option to chose "Serverless" is greyed out...
What am I missing?
OK, so the information in the documentation here is very unclear: https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-serverless-v2.upgrade.html#aurora-serverless-v2.upgrade-from-serverless-v1-procedure
You shouldn't try to migrate the Cluster from Provisioned to Serverless, the option is to convert the DATABASE (Writer instance) in the Provisioned Cluster to Serverless V2!
So, here's the steps that might save someone else a few tries (and hours):
Create a Snapshot for the existing Aurora Serverless Cluster overview page (takes about 5 minutes (depending on DB size))
Open snapshots and choose to restore Snapshot to highest available PROVISIONED Aurora Cluster (for me it was Postgres 10.20), no other settings needs to be changed other than "Provisioned" and the version (this will take several minutes, about 15 minutes)
Refresh now and again using the "refresh" button (as the AWS console "refresh" isn't very reliable) to see when the cluster is ready (database doesn't need to be ready, only the Cluster!)
Once the Cluster is "available", open the Cluster and click "Modify"
Choose the DB engine version as 13.6 (this is the only version working for Aurora Serverless v2) then scroll down and click "Continue"
Select "Apply immediately" and click "Modify Cluster"
Back on the Cluster overview page, again wait for the Cluster to upgrade (this will take several minutes, about 20 minutes)
Once the Cluster and database are available, select the DATABASE and choose "Modify"
Select Serverless v2 and then "Continue"
Choose to apply Immediately and modify the database
Wait for it to modify completely and you'll have your new Serverless V2 done!
Another thing to note is that with Aurora V2 we'll apparently have a Cluster and a database attached:
I'd assume this is because with Serverless V2 (which is pretty cool!) you can attach additional read replica databases which will "off-load" your writer instance making it faster...
add on on #anders answer, your rds instances must be one of the instance type from this list else it will throw below error.
for supported combinations of instance class and database engine version, see the documentation.

Is it possible to switch an Aurora RDS instance from serverless to instance?

Is it possible to switch an Aurora RDS instance from the serverless "role" to the instance role? I don't see any way to edit the "Role" field in AWS.
You can restore but you can't switch roles or change db type on the fly.
You'd need to take a snapshot of your RDS Aurora and restore it, but keep in mind that Aurora Serverless has its requirements, for example regarding engine version.
Engine versions for Aurora Serverless V1
Engine versions for Aurora Serverless V2
And here's how to restore an Aurora DB Severless from a snapshot.

Can we use AWS Data Migration Service for replication from Aurora Serverless as source?

My DMS replication instance (which is in same VPC as of Aurora serverless DB instance) is not able to find DB while creating endpoint in DMS.
However, I am able to create a cloud9 instance in same VPC as aurora serverless instance and connect to it from there.
Am I missing something here or it is not possible to use AWS DMS for migrating data from Aurora serverless as source?
Above issue was resolved by explicitly specifying the connection details for aurora serverless cluster (instead of dropdown selection). But the answer to original question of using Aurora serverless DB as source in DMS replication -
Yes, if only one time replication is required
No, If ongoing replication is required. For ongoing replication, It is required to change the values of binlog_format parameter for source database. Although, Aurora serverless allows changing value for this parameter but it has no impact in actual. Only a few parameters are supported for change which are listed here