aws-rds: add metricReadIOPs method to DatabaseClusterFromSnapshot

[jbcitian]

Describe the feature

Currently, DatabaseClusterFromSnapshot only has a method for metricVolumeReadIOPs. It would be helpful to add a metricReadIOPs method to track the ReadIOPs metric at the cluster level

Use Case

I'm trying to satisfy Drata compliance controls. Their docs for I/O monitoring suggest configuring an alarm on ReadIOPs, which is possible in the console, but not possible using CDK. This would be especially helpful because if you configure a cluster-level metric, you don't then have to also configure a metric for each reader/writer instance.

Proposed Solution

No response

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

AWS CDK Library version (aws-cdk-lib)

2.212.0

AWS CDK CLI version

2.1026.0

Environment details (OS name and version, etc.)

Sequoia 15.6

[pahud]

Hi @jbcitian,

Thank you for this feature request! You're absolutely right that having a metricReadIOPs method would be helpful for monitoring database I/O at the cluster level, especially for compliance requirements like Drata.

I can confirm that AWS CloudWatch does support the ReadIOPS metric for RDS instances, and it makes sense to expose this through the CDK alongside the existing metricVolumeReadIOPs method. The difference would be:

• metricVolumeReadIOPs() - Cluster-level billed read operations from the Aurora cluster volume
• metricReadIOPs() - Instance-level read I/O operations per second (which can be aggregated across instances)

This is a straightforward enhancement that would follow the existing pattern in the DatabaseClusterNew class, similar to how metricServerlessDatabaseCapacity and metricACUUtilization are implemented.

The implementation would add the method to the base class, making it available to both DatabaseCluster and DatabaseClusterFromSnapshot automatically.

Would you be interested in contributing this feature? It would be a great addition to the CDK! The implementation should be relatively straightforward - adding a new method that calls this.metric('ReadIOPS', { statistic: 'Average', ...props }) following the established pattern.

Let me know if you'd like to work on this or if you have any questions about the implementation approach.

[jasdeepbhalla]

@pahud: Thanks for the great suggestion! I’ve opened a PR to add this feature. I’d love your feedback on it. Thanks :)

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.