ElastiCache Clusters (Inventory)

Ensure that your AWS ElastiCache Reserved Cache Nodes are renewed before expiration date.

Make sure the number of ElastiCache cluster cache nodes provisioned in your AWS account has not reached the limit set by your organization. Monitoring and setting limits will assist you to handle your resources better and avoid unforeseen costs in your AWS bill.

Sends a report if Any of the Elasticache cluster present in your AWS account is appeared to be idle. Identifying and removing idle resources is a great practice to reduce AWS cost.

.

Ensure that your ElastiCache Redis Cache clusters are using a Multi-AZ deployment configuration to enhance High Availability (HA). To determine if your ElastiCache Redis Cache clusters are using a Multi-AZ configuration.

Setting limits for the type of AWS ElastiCache cluster nodes will help you address internal compliance requirements and prevent unexpected charges on your AWS bill. Ensure that your existing AWS ElastiCache cluster nodes have the desired type established by your organization based on the caching workload required.

Amazon ElastiCache clusters using EC2-VPC platform instead of EC2-Classic can bring multiple advantages such as better flexibility and control over the cache clusters security, availability, traffic routing and more. This template ensure that your ElastiCache clusters are provisioned within the AWS EC2-VPC platform or not.

Send a report of ElastiCache clusters without a cloudwatch alarm attached to them.

Sends a report of Elasticache clusters if there CPU utilization goes above than 90 %. Clusters with high CPUUtilization should be rebooted this will improve the performance.

Enabling the Multi-AZ Automatic Failover feature for your Redis Cache clusters will improve the fault tolerance in case the read/write primary node becomes unreachable due to loss of network connectivity, loss of availability in the primary’s AZ, etc. This template this feature for your ElastiCache cluster.

AWS ElastiCache Redis clusters are encrypted in order to meet security and compliance requirements. Data encryption helps prevent unauthorized users from reading sensitive data available on your Redis clusters and their associated cache storage systems. It is highly recommended to implement encryption in order to protect it from unauthorized access and fulfill compliance requirements for data-at-rest and in-transit encryption within your organization.

A payment-pending ElastiCache RCN purchase is a reservation purchase that can`t be fully processed due to issues with the payment method utilized The cost savings when using ElastiCache Reserved Cache Nodes over standard On-Demand Cache Nodes are up to 70% when used in steady state, therefore in order to receive this discount benefit you need to make sure that all your ElastiCache reservation purchases have been fully processed.

A failed ElastiCache RCN is an unsuccessful reservation that received the "payment-failed" status during the purchase process. The cost savings when using ElastiCache Reserved Cache Nodes over standard On-Demand Cache Nodes are up to 70% when used in steady state, therefore in order to receive this discount benefit you need to make sure that all your ElastiCache reservation purchases have been successfully completed.

Checking your ElastiCache Reserved Cache Nodes on a regular basis you can detect and cancel any unwanted purchases placed within your AWS account and avoid unexpected charges on your AWS monthly bill. Ensure that all Amazon ElastiCache Reserved Cache Node (RCN) purchases are reviewed every 7 days.