1 Answer
- Newest
- Most votes
- Most comments
0
hi ,buddy , For OpenSearch instances, the fee for m6g.xlarge.search should be halved after reserving m6g.large.search. But in your case, the cost of m6g.xlarge.search remains unchanged. This is most likely due to the following reasons:
- Reserved instances only apply to the specific reserved instance types, not to larger instance types. That is to say, reserving m6g.large.search instances will only halve the cost of m6g.large.search, not the cost of m6g.xlarge.search.
- The number of reserved instances you purchased is not enough to cover the number of m6g.xlarge.search instances you used. The discounts of reserved instances only apply to instances that reserved instances can cover. The excess will be billed at on-demand rates.
- Your OpenSearch cluster may use a mix of on-demand instances and reserved instances. In this case, reserved instances will only discount portions for reserved instances, and the cost of on-demand instances will remain unchanged.
- The period you purchased the reserved instances does not match the period you are running the m6g.xlarge.search instances. Discounts for reserved instances only apply to the purchased reservation period, and instance costs outside that period are not discounted.
- Your current billing cycle has not ended yet, meaning you have not started enjoying the benefits of reserved instances. Discounts for reserved instances usually take effect the next billing cycle.
answered a year ago
Relevant content
- Accepted Answerasked a year ago
- asked 3 years ago
- asked a year ago
- asked a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
Thank you! I think it is due to reason 1. But how to fix this? I do not want to half our instance type because that is too small. Should I install 2 times m6g.large.search then? And is that still possible after reserving 1 time m6g.large.search?