Discrepancy in RDS Compute Costs between the platform and AWS console

Products

• CloudHealth

Issue/Introduction

This may be caused when a RDS reservation is retired early before their expected expiration time.

In that case, the reservation State changes to retired, but the platform does not have a clear way to discover when the reservation was retired since current AWS APIs don't provide an actual end time.  Instead, the platform assumes that the end_date is when the state first appears as retired.  Ultimately this results in miscalculations of RDS - Unused RIs when we use these times to map reservation pricing across time.

Resolution

Please submit a ticket with Technical Support to complete an "RDS - Unused RIs" cost correction if you are facing a similar issue as described above.