RDS Reserved Instance no longer supported

0

Hello, how are you? Please, I need your urgent help, a couple of days ago I acquired an Aurora Mysql RDS reserved instance of class t3.small, when I want to create a database that meets these specifications so that the reserved instance can be used, I find that there is no configuration with the current Aurora Mysql for a t3.small instance, and only lets me choose a t3.small instance if I go down to version 5. 7 of Aurora Mysql, the problem is that by doing this, it forces me to subscribe to extended support, which will represent extremely high costs, which I want to avoid, please if someone can give me any option or solution I would be very grateful because the instance is new and I would not want to lose money, I would also like to know what would happen if I do the update of the cluster to a t3.medium, as would be the costs taking into account that I have my instance reserved t3.small.

Thank you very much for your help.

2 Answers
0

I understand your concern regarding the RDS Reserved Instance you recently acquired. Let me address your situation and provide some insights.

First, it's important to note that Amazon RDS for MySQL 5.7 is reaching the end of its standard support on February 29, 2024. After this date, instances running MySQL 5.7 will be automatically enrolled in Extended Support, which does indeed come with additional costs.

Regarding your specific situation with the t3.small Reserved Instance for Aurora MySQL, it appears that the latest versions of Aurora MySQL may no longer support the t3.small instance class. This is likely due to performance considerations for newer versions of the database engine.

As for your options:

  1. If you absolutely need to use a t3.small instance, you might consider using RDS for MySQL instead of Aurora MySQL. RDS for MySQL still supports t3.small instances in more recent versions.

  2. If you decide to upgrade to a t3.medium instance, your t3.small Reserved Instance can still provide some benefit. Amazon RDS offers size-flexible Reserved Instances, which means your t3.small reservation can be applied to a t3.medium instance, albeit only covering a portion of its cost. The discount will be applied based on the relative size difference between t3.small and t3.medium.

  3. If neither of these options work for your use case, you may want to contact AWS Support to discuss your situation. They might be able to offer more specific guidance or potentially assist with exchanging your Reserved Instance if it's very new.

Remember, the goal of Reserved Instances is to optimize costs based on expected usage. If your needs have changed since purchasing the Reserved Instance, it might be worth reassessing your requirements and potentially adjusting your reservation strategy.

Lastly, keep in mind that while upgrading to a newer version might seem costly in the short term, it often provides benefits in terms of performance, security, and access to new features that could be valuable for your applications in the long run.
Sources
[Announcement] Amazon RDS Extended Support opt-in behavior is changing. Upgrade your Amazon RDS for MySQL 5.7 database instances before February 29, 2024 to avoid potential increase in charges. | AWS re:Post
AWS Services that support reserved nodes size flexibility or reserved instances size flexibility | AWS re:Post
Reserved DB instances for Amazon RDS - Amazon Relational Database Service

profile picture
answered 2 months ago
profile picture
EXPERT
reviewed 2 months ago
0

What you can also do is purchase another t3.small which when combined with the other t3.small will make the equivalent of a t3.medium

profile picture
EXPERT
answered 2 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions