Videos
I mistakenly created an RDS reserved instance for a db.m3.medium when i meant to use a db.m5.large and i'm wondering if its too late to change?
related to this oopsie, if i create a reserved instance with multi-az, is it possible to use it for an instance that does not use multi-az?
Hi so I wanted my mysql RDS instance upgraded to 5.7.21.
However the issue is I have a reserved instance for 1 year term running mysql 5.5.53.
I tried upgrading the 5.5.53 instance but it will only let me upgrade upto 5.6.x
My question is, can I move the reserved instance remaining days to a new instance with mysql version 5.7.21 ? Kindly assist. Thanks!
I don't believe the reserved instance has got anything to do with your software version. There must be some other reason why you're having trouble upgrading. Keep in mind the reserved instance is a billing construct and it isn't actually tied directly to that RDS instance. You can spin up another and delete the existing one and the RI will apply to the new one as long as the instance type and licensed (MySQL) match
u/philsw is correct, the fact it's a reserved instance is irrelevant.
With MySQL and Postgres you can only migrate one major version up, this means you have to upgrade in two steps:
5.5 -> 5.6
5.6 -> 5.7
Hi,
My question is, is it possible to change my already running on-demand priced MySQL database to reserved pricing? I saw some references that it is possible with EC2 instances, but I couldn't find anything similar for RDS.
Thanks!
Reserved instances are a billing construct only.
If you buy a reserved instance for a m1.small in us-west-2a, all that means is that one of your on-demand RDS instances that's an m1.small in us-west-2a receives that lower hourly price (and incidentally, if you delete that instance and make a new one, the reservation's lower hourly rate just shifts onto the new instance). No instance is launched by reserving one.
Think of it as purchasing a licence for one of your existing instances you already have rather than creating a new instance.