Viewing ElastiCache Node Status - Amazon ElastiCache for Redis
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Viewing ElastiCache Node Status

Using the ElastiCache console, you can quickly access the status of your ElastiCache node. The status of an ElastiCache node indicates the health of the node. You can use the following procedures to view the ElastiCache node status in the Amazon ElastiCache console, the Amazon CLI command, or the API operation.

The possible status values for ElastiCache nodes are in the following table. This table also shows if you will be billed for the ElastiCache node.

Type Billed Description

available

Billed

The ElastiCache node is healthy and available.

creating

Not billed

The ElastiCache node is being created. The Node is inaccessible while it is being created.

deleting

Not billed

The ElastiCache node is being deleted.

modifying

Billed

The ElastiCache node is being modified because of a customer request to modify the node.

updating

Billed

An Updating state indicates one or more of the following is true of the Amazon Elasticache node:

rebooting cache cluster nodes

Billed

The ElastiCache node is being rebooted because of a customer request or an Amazon ElastiCache process that requires the rebooting of the node.

incompatible_parameters

Not billed

Amazon ElastiCache can't start the node because the parameters specified in the node's parameter group aren't compatible with the node. Either revert the parameter changes or make them compatible with the node to regain access to your node. For more information about the incompatible parameters, check the Events list for the ElastiCache node.

incompatible_network

Not billed

An incompatible-network state indicates one or more of the following is true of the Amazon ElastiCache node:

  • There are no available IP addresses in the subnet that the ElastiCache node was launched into.

  • The subnet mentioned in the ElastiCache subnet group no longer exists in the Amazon Virtual Private Cloud (Amazon VPC).

restore_failed

Not billed

A restore-failed state indicates one of the following is true of the Amazon ElastiCache node:

  • Replacements of node failed due to Insufficient instance capacity repeatedly. This typically happens when running previous generation nodes that are end-of-life. However, it could also happen with replacement of current generation nodes when Amazon does not have enough on-demand capacity to fulfill your request in the specified Availability Zone. For more information on fixing or removing these nodes, see Migrating previous generation nodes.

  • The specified RDB snapshot failed to restore.

  • The Amazon account for the ElastiCache cluster has been suspended.

  • The node failed and could not be recovered.

snapshotting

Billed

ElastiCache is creating a snapshot of the ElastiCache for Redis node.

Viewing ElastiCache Node Status with the console

To view the status of an ElastiCache Node with the console:

  1. Sign in to the Amazon Web Services Management Console and open the Amazon ElastiCache console at https://console.aws.amazon.com/elasticache/.

  2. In the navigation pane, choose Redis Clusters or Memcached Clusters. The Caches page appears with the list of ElastiCache Nodes. For each node, the status value is displayed.

  3. You can then navigate to the Service Updates tab for the cache to display the list of service Updates applicable to the cache.

Viewing ElastiCache Node Status with the Amazon CLI

To view ElastiCache node and its status information by using the Amazon CLI, use the describe-cache-cluster command. For example, the following Amazon CLI command displays each ElastiCache node.

aws elasticache describe-cache-clusters

Viewing ElastiCache Node Status through the API

To view the status of the ElastiCache node using the Amazon ElastiCache API, call the DescribeCacheClusteroperation with the ShowCacheNodeInfo flag to retrieve information about the individual cache nodes.