Skip to main content

Triage AWS ElastiCache Low Connection Count ELASTICACHE_CLUSTER_UNUSED

  1. Configure AWS ElastiCache Low Connection Count
  2. Use Case for AWS ElastiCache Low Connection Count
  3. Triage Guides by Violation Type
    1. Triage AWS ElastiCache Low Connection Count ELASTICACHE_CLUSTER_UNUSED

Triage Guide for ElastiCache Cluster Unused

Understand​

Why should I care about fixing this issue?

  • An unused ElastiCache cluster incurs costs without providing value. Decommissioning it can save resources and budget.

Validate​

How am I sure that this alert is true and accurate?

  • The alert is based on CloudWatch's CurrConnections metric. To verify manually, inspect the metric in the CloudWatch console under the corresponding cluster ID.

Does this policy scan on a schedule or is it Reactive?

  • It is reactive, based on the passage of time and changing metrics.

When does it scan?

  • The policy evaluates once every 24 hours by default.

Triage​

What is the impact if it is unfixed?

  • Continual unnecessary costs accrue from maintaining the idle cluster.

Does this problem get worse over time if it is unaddressed?

  • Financially, the wasteful expenditure will compound over time.

Can remediation cause outages or downtime to any other running service?

  • If the cluster is truly unused, there should be no impact on other services. Verify usage before decommissioning.

Act​

What do I do to fix this alarm?

  • Assess the business impact and decide whether to decompress or repurpose the cluster. Follow AWS procedures for safely decommissioning or reconfiguring ElastiCache clusters.

Reflect​

What should I do if this alarm wasn't a good use of time?

  • Reconsider the thresholds set in the policy to better reflect usage patterns. Adjust the inactivityPeriod and activityThreshold as necessary or disable the policy if it does not align with organizational goals.