On a 1-year no-upfront RI, db.m6g.large costs almost the same as db.t4g.large.
| Instance | On-demand | RI effective | RI monthly | Savings |
|---|---|---|---|---|
| db.t4g.large | $0.167/hr | $0.132/hr | $96.43 | 21% |
| db.m6g.large | $0.214/hr | $0.137/hr | $100.16 | 36% |
On-demand, t4g is ~22% cheaper. With an RI the gap is just ~$3.70/month, and m6g gives you:
Verdict: for a production database you're reserving, m6g.large RI is the better buy. Use t4g on-demand for dev/staging. https://aws.amazon.com/rds/mysql/pricing/?pg=pr&loc=2&trk=12e10b21-1188-462a-b0c4-c5d2bdad96df&sc_channel=ps&refid=12e10b21-1188-462a-b0c4-c5d2bdad96df
| Instance | On-demand | RI effective | RI monthly | Savings |
|---|---|---|---|---|
| db.t4g.large | $0.167/hr | $0.132/hr | $96.43 | 21% |
| db.m6g.large | $0.214/hr | $0.137/hr | $100.16 | 36% |
On-demand, t4g is ~22% cheaper. With an RI the gap is just ~$3.70/month, and m6g gives you:
- Full 2 vCPU all the time. t4g.large has a ~30% CPU baseline.
- No surplus credit charges. These aren't covered by the RI.
- No throttling during spikes.
Verdict: for a production database you're reserving, m6g.large RI is the better buy. Use t4g on-demand for dev/staging. https://aws.amazon.com/rds/mysql/pricing/?pg=pr&loc=2&trk=12e10b21-1188-462a-b0c4-c5d2bdad96df&sc_channel=ps&refid=12e10b21-1188-462a-b0c4-c5d2bdad96df