AWS Amazon ElastiCache Error Codes

The customer has exceeded the allowed rate of API calls.

The specified Amazon EC2 security group is already authorized for the specified cache security group.

The specified Amazon EC2 security group is not authorized for the specified cache security group.

You already have a cluster with the given identifier.

The requested cluster ID does not refer to an existing cluster.

A cache parameter group with the requested name already exists.

The requested cache parameter group name does not refer to an existing cache parameter group.

The request cannot be processed because it would exceed the maximum number of cache security groups.

A cache security group with the specified name already exists.

The requested cache security group name does not refer to an existing cache security group.

The request cannot be processed because it would exceed the allowed number of cache security groups.

The requested cache subnet group name is already in use by an existing cache subnet group.

The requested cache subnet group is currently in use.

The requested cache subnet group name does not refer to an existing cache subnet group.

The request cannot be processed because it would exceed the allowed number of cache subnet groups.

The request cannot be processed because it would exceed the allowed number of subnets in a cache subnet group.

The request cannot be processed because it would exceed the allowed number of clusters per customer.

The default user assigned to the user group.

You must add default user to a user group.

A user with this username already exists.

The Global datastore name already exists.

The Global datastore does not exist

The requested cache node type is not available in the specified Availability Zone. For more information, see InsufficientCacheClusterCapacity in the ElastiCache User Guide.

The requested Amazon Resource Name (ARN) does not refer to an existing resource.

The requested cluster is not in the available state.

The current state of the cache parameter group does not allow the requested operation to occur.

The current state of the cache security group does not allow deletion.

You must enter valid credentials.

The Global datastore is not available or in primary-only state.

The KMS key supplied is not valid.

Two or more incompatible parameters were specified.

The value for a parameter is invalid.

The requested replication group is not in the available state.

The state of the serverless cache snapshot was not received. Available for Valkey, Redis OSS and Serverless Memcached only.

The account for these credentials is not currently active.

The current state of the snapshot does not allow the requested operation to occur.

An invalid subnet identifier was specified.

The user group is not in an active state.

The user is not in active state.

The VPC network is in an invalid state.

The node group specified by the NodeGroupId parameter could not be found. Please verify that the node group exists and that you spelled the NodeGroupId value correctly.

The request cannot be processed because it would exceed the maximum allowed number of node groups (shards) in a single replication group. The default maximum is 90

The request cannot be processed because it would exceed the allowed number of cache nodes in a single cluster.

The request cannot be processed because it would exceed the allowed number of cache nodes per customer.

The operation was not performed because no changes were required.

The specified replication group already exists.

The targeted replication group is not available.

The specified replication group does not exist.

The designated replication group is not available for data migration.

You already have a reservation with the given identifier.

The requested reserved cache node was not found.

The request cannot be processed because it would exceed the user's cache node quota.

The requested cache node offering does not exist.

A serverless cache with this name already exists.

The serverless cache was not found or does not exist.

The number of serverless caches exceeds the customer quota.

A serverless cache snapshot with this name already exists. Available for Valkey, Redis OSS and Serverless Memcached only.

This serverless cache snapshot could not be found or does not exist. Available for Valkey, Redis OSS and Serverless Memcached only.

The number of serverless cache snapshots exceeds the customer snapshot quota. Available for Valkey, Redis OSS and Serverless Memcached only.

The specified service linked role (SLR) was not found.

The service update doesn't exist

You already have a snapshot with the given name.

You attempted one of the following operations: Creating a snapshot of a Valkey or Redis OSS cluster running on a cache.t1.micro cache node. Creating a snapshot of a cluster that is running Memcached rather than Valkey or Redis OSS. Neither of these are supported by ElastiCache.

The requested snapshot name does not refer to an existing snapshot.

The request cannot be processed because it would exceed the maximum number of snapshots.

The requested subnet is being used by another cache subnet group.

At least one subnet ID does not match the other subnet IDs. This mismatch typically occurs when a user sets one subnet ID to a regional Availability Zone and a different one to an outpost. Or when a user sets the subnet ID to an Outpost when not subscribed on this service.

The requested tag was not found on this resource.

The request cannot be processed because it would cause the resource to have more than the allowed number of tags. The maximum number of tags permitted on a resource is 50.

The TestFailover action is not available.

A user with this ID already exists.

The user group with this ID already exists.

The user group was not found or does not exist

The number of users exceeds the user group limit.

The user does not exist or could not be found.

The quota of users has been exceeded.