Package-level declarations
Types
An ACL with the specified name already exists.
The specified ACL does not exist.
Returns the updates being applied to the ACL.
The request cannot be processed because it would exceed the maximum number of ACLs allowed.
The status of the ACL update
The customer has exceeded the maximum number of API requests allowed per time period.
Denotes the user's authentication properties, such as whether it requires a password to authenticate. Used in output responses.
Denotes the user's authentication properties, such as whether it requires a password to authenticate. Used in output responses.
Indicates if the cluster has a Multi-AZ configuration (multiaz) or not (singleaz).
A cluster with the specified name already exists.
A list of cluster configuration options.
The specified cluster does not exist.
A list of updates being applied to the cluster
The request cannot be processed because it would exceed the maximum number of clusters allowed for this customer.
A default user is required and must be specified.
A user with the specified name already exists.
Provides details of the Redis OSS engine version
The cluster does not have sufficient capacity to perform the requested operation.
The ACL is not in a valid state for the requested operation.
The specified Amazon Resource Name (ARN) is not valid.
The cluster is not in a valid state for the requested operation.
The provided credentials are not valid.
The specified KMS key is not valid or accessible.
The requested operation cannot be performed on the multi-Region cluster in its current state.
The node is not in a valid state for the requested operation.
The specified parameter combination is not valid.
The parameter group is not in a valid state for the requested operation.
The specified parameter value is not valid.
The snapshot is not in a valid state for the requested operation.
The specified subnet is not valid.
The user is not in a valid state for the requested operation.
The VPC network is not in a valid state for the requested operation.
Base class for all service related exceptions thrown by the MemoryDb client
Represents a multi-Region cluster.
A multi-Region cluster with the specified name already exists.
The specified multi-Region cluster does not exist.
Describes an individual setting that controls some aspect of MemoryDB behavior across multiple regions.
Represents the output of a CreateMultiRegionParameterGroup operation. A multi-region parameter group represents a collection of parameters that can be applied to clusters across multiple regions.
The specified multi-Region parameter group does not exist.
The request cannot be processed because it would exceed the maximum number of nodes allowed for this cluster.
The request cannot be processed because it would exceed the maximum number of nodes allowed for this customer.
The requested operation would result in no changes.
Represents the output of a CreateParameterGroup operation. A parameter group represents a combination of specific values for the parameters that are passed to the engine software during startup.
A parameter group with the specified name already exists.
The specified parameter group does not exist.
The request cannot be processed because it would exceed the maximum number of parameter groups allowed.
Describes a name-value pair that is used to update the value of a parameter.
Update action that has yet to be processed for the corresponding apply/stop request
The recurring charge to run this reserved node.
Represents a Regional cluster
A request to configure the number of replicas in a shard
Represents the output of a PurchaseReservedNodesOffering
operation.
You already have a reservation with the given identifier.
The requested node does not exist.
The request cannot be processed because it would exceed the user's node quota.
The offering type of this node.
The requested node offering does not exist.
The status of the online resharding
Represents a single security group and its status.
The required service-linked role was not found.
An update that you can apply to your MemoryDB clusters.
The specified service update does not exist.
A request to apply a service update
Shard configuration options. Each shard configuration has the following: Slots and ReplicaCount.
A request to configure the sharding properties of a cluster
Provides details of a shard in a snapshot
The specified shard does not exist.
The request cannot be processed because it would exceed the maximum number of shards allowed per cluster.
Represents the progress of an online resharding operation.
A snapshot with the specified name already exists.
The specified snapshot does not exist.
The request cannot be processed because it would exceed the maximum number of snapshots allowed.
Represents the output of one of the following operations:
A subnet group with the specified name already exists.
The subnet group is currently in use and cannot be deleted.
The specified subnet group does not exist.
The request cannot be processed because it would exceed the maximum number of subnet groups allowed.
The subnet is currently in use and cannot be deleted.
The specified subnet is not allowed for this operation.
The request cannot be processed because it would exceed the maximum number of subnets allowed.
A tag that can be added to an MemoryDB resource. Tags are composed of a Key/Value pair. You can use tags to categorize and track all your MemoryDB resources. When you add or remove tags on clusters, those actions will be replicated to all nodes in the cluster. A tag with a null Value is permitted. For more information, see Tagging your MemoryDB resources
The specified tag does not exist.
The request cannot be processed because it would exceed the maximum number of tags allowed per resource.
Test failover is not available for this cluster configuration.
A cluster whose updates have failed
A user with the specified name already exists.
The specified user does not exist.
The request cannot be processed because it would exceed the maximum number of users allowed.