- Newest
- Most votes
- Most comments
Hello.
Reserved Instances provide discounted pricing for specific DB instance types.
Reserved Instances are applied to the "region", "DB engine", "instance type", etc. that match the settings at the time of purchase, so I don't think there is an option to apply them when starting an RDS instance.
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_WorkingWithReservedDBInstances.html
For example, when you purchase an Oracle t2.micro Reserved Instance, the discount will be automatically applied to the currently running On-Demand Instance t2.micro RDS Oracle.
We recommend that you check the following document for details regarding Reserved Instances.
https://aws.amazon.com/rds/reserved-instances/?nc1=h_ls
To purchase RDS Reserved Instances, follow the steps in the document below.
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_WorkingWithReservedDBInstances.html#USER_WorkingWithReservedDBInstances.WorkingWith
That's correct, you specify the instance type that you want to purchase on that page, and once that's complete the instance will appear in the Reserved Instances section of the RDS Console. From here you configure storage, backups, etc.
See the section How To Purchase Reserved Instances of https://aws.amazon.com/rds/reserved-instances/
Also be aware of the four important bulletpoints in the section Important Notes about Purchases at the foot of that page.
Are you saying first I create the reserved instance and after that I can click on the link for it and configure all the other information for RDS such as master account userid/password, backups, storage, monitoring, etc afterwards similar to an on-demand RDS?
I was testing creating one but I dont recall seeing this info for configuration.
The poroblem also with Reserved Instances is that I cannot delete it afterwards and I am stuck with the charges for it.
Thanks,
Are you saying first I create the reserved instance
First you purchase the reserved instance, and once it's paid for you are able to start configuring it. Reserved instances are just a billing construct, the technology underneath it is exactly the same as an on-demand instance.
If you know for a fact that you're going to need this database 24x7x365 then you can pony up for a whole year in advance and it's cheaper. Equally if you're not sure that the instance type is right for you - and you mention in your comment about deleting it afterwards - then stick with on-demand instances at least to start with.
You can always start with on-demand, and after a couple of months you know that this instance type is right for the workload that is being run on it, you can convert from on-demand to reserved at that point https://aws.amazon.com/rds/reserved-instances/
If you purchase a Reserved Instance in a given region where you have a applicable running DB instance, the benefit will automatically be applied to that instance moving forward.
So if i have several on-demand RDS instances running now with similar instance type, DB engine and I want to change one RDS instance to Reserverd Instance, I just purchase a reserved instance and AWS will automatically change any one of those instances to "Reserved"? Is there a way to tell AWS which one exactly I need to change to Reserved or know which one it selected?
This is addressed in https://aws.amazon.com/rds/pricing/
How do the Reserved Instance payment options impact my bill?
The Amazon RDS operations for creating, modifying, and deleting DB instances do not distinguish between On-Demand and Reserved Instances (RIs). Our system will automatically apply your reservation(s) such that all eligible DB instances are charged at the lower hourly reserved DB instance rate.
That does not explain the situation though. In my case I have 5 RDS intances with similar config (DEV, TEST, PROD1, PROD2, PROD3). I have a requirement to make PROD3 a Reserved Instance. Based on your explanation, there is no way to guarantee that that and AWS can apply the Reservation to any of the 5 instances if they have similar specs. Is this correct?
Relevant content
- asked a year ago
- asked 10 months ago
AWS OFFICIALUpdated 9 months ago- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 3 months ago
Excellent Inormation! However, for RDS Reserved dont you need to configure the RDS similar to how you configure an on-demand RDS ? I dont see any data entry on reserved RDS form to configure master account userid/password, backups frequency, monitoring, storage size, snapshots, database name, etc. .
Do you configure these somewhere else or they are not available with Reserved RDS? Is there a link in documentation that shows steps for that?
Thanks,
Reserved Instances are automatically applied to On-Demand Instances that match the "region", "DB engine", "instance type", etc. that were set at the time of purchase. In other words, if you first launch an On-Demand Instance and then purchase a Reserved Instance, it will be applied automatically. The document I shared says: Therefore, there is no problem with password, monitoring, and backup settings as long as you create an on-demand instance as usual. https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_WorkingWithReservedDBInstances.html
So basically you create an on-demand RDS first and configure it, and then you create the reserved instance with identical specs which will change the pricing for on-demand instance to reserved?
Can I also create the Reserved Instance First and then create the RDS instance with identical specs or not?
What about if I have multiple RDS on-demand instance with identical specs but I only want to select one to be Reserved instance. How does AWS link the reserved one to the on-demand one if they all have same Region, instance Type, and DB Engine?
This applies automatically if you purchase Reserved Instances in the same instance type and region as On-Demand Instances.
In that case, it is not possible to decide which instance it will be assigned to. Yes. It is possible.
In that case, it is not possible to decide which instance it will be assigned to. AWS will automatically decide.
If I understand you correctly, for the case if we have multiple RDS instances with similar specs (DEV, TEST, PROD1, PROD2, PROD3) and I have a requirement to purchase a Reserved Intance for PROD3, there is no way to know or guarantee what RDS instance AWS will select for for the Reserved INstance. Is this correct?