Skip to main content

Use Case for AWS ElastiCache Low Connection Count

  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

AWS ElastiCache Low Connection Count

Why use this policy?​

Pros:​

  • Cost Optimization: Identifying unused ElastiCache clusters can significantly reduce unnecessary costs.
  • Resource Management: Helps in decluttering the environment by highlighting resources that are not being utilized by applications.
  • Performance Impact: Removing or archiving idle resources can improve the management console performance.

Cons:​

  • Potential Service Disruption: If a cluster is incorrectly identified as unused, it might be wrongly terminated.

How the policy works:​

This policy checks if an AWS ElastiCache cluster has had no requests (connections) in the last 30 days. It uses CloudWatch's CurrConnections metric, normalized to requests per day.

Configuration Variables​

  • inactivityPeriod: The number of days to check for activity. Default: 30
  • activityThreshold: The minimum number of requests per day to consider the cluster active. Default: 0

Violation Types​

  • ELASTICACHE_CLUSTER_UNUSED: Indicates the cluster has had less activity than the threshold set and may be a candidate for decommissioning.

The distinction between violationTypeIds lies in the specific condition that triggers each violation, here being the lack of activity on an ElastiCache cluster based on the defined threshold.