Triage AWS RDS DBClusters should leverage ARM instances NON_ARM_INSTANCE_TYPE_USED
Quick Links
- Configure AWS RDS DBClusters should leverage ARM instances
- Use Case for AWS RDS DBClusters should leverage ARM instances
- Triage Guides by Violation Type
Triage Guide for NON_ARM_INSTANCE_TYPE_USED
Understand
Why should I care about fixing this issue?
Moving to ARM instance types can result in cost savings and potentially better performance, depending on your workloads.
Validate
How am I sure that this alert is true and accurate?
This policy evaluates the instance types based on the DescribeDBClusters API call. To verify manually, you can use the AWS Management Console or AWS CLI to inspect the instance types for your DBClusters.
Does this policy scan on a schedule or is it Reactive?
The policy is reactive and should be evaluated when changes are made to AWS RDS DBCluster configurations.
Triage
What is the impact if it is unfixed?
Continued use of non-ARM instance types may lead to unnecessary expenses.
Does this problem get worse over time if it is unaddressed?
Yes, as you continue to incur higher costs.
Can remediation cause outages or downtime to any other running service?
Switching instances may result in some downtime during migration. Plan accordingly to minimize service disruption.
Act
What do I do to fix this alarm?
Transition your RDS DBClusters to supported ARM instance types that meet your application requirements and performance needs.
Reflect
What should I do if this alarm wasn't a good use of time?
Review your workloads and application requirements. If ARM instances are not suitable, mark these RDS DBClusters as exceptions with proper justification or adjust the policy to reflect your organizational standards and needs.