MemoryDB#
Client#
- class MemoryDB.Client#
A low-level client representing Amazon MemoryDB
MemoryDB is a fully managed, Redis OSS-compatible, in-memory database that delivers ultra-fast performance and Multi-AZ durability for modern applications built using microservices architectures. MemoryDB stores the entire database in-memory, enabling low latency and high throughput data access. It is compatible with Redis OSS, a popular open source data store, enabling you to leverage Redis OSS’ flexible and friendly data structures, APIs, and commands.
client = session.create_client('memorydb')
These are the available methods:
- batch_update_cluster
- can_paginate
- close
- copy_snapshot
- create_acl
- create_cluster
- create_multi_region_cluster
- create_parameter_group
- create_snapshot
- create_subnet_group
- create_user
- delete_acl
- delete_cluster
- delete_multi_region_cluster
- delete_parameter_group
- delete_snapshot
- delete_subnet_group
- delete_user
- describe_acls
- describe_clusters
- describe_engine_versions
- describe_events
- describe_multi_region_clusters
- describe_parameter_groups
- describe_parameters
- describe_reserved_nodes
- describe_reserved_nodes_offerings
- describe_service_updates
- describe_snapshots
- describe_subnet_groups
- describe_users
- failover_shard
- get_paginator
- get_waiter
- list_allowed_multi_region_cluster_updates
- list_allowed_node_type_updates
- list_tags
- purchase_reserved_nodes_offering
- reset_parameter_group
- tag_resource
- untag_resource
- update_acl
- update_cluster
- update_multi_region_cluster
- update_parameter_group
- update_subnet_group
- update_user
Client Exceptions#
Client exceptions are available on a client instance via the exceptions property. For more detailed instructions and examples on the exact usage of client exceptions, see the error handling user guide.
The available client exceptions are:
- ACLAlreadyExistsFault
- ACLNotFoundFault
- ACLQuotaExceededFault
- APICallRateForCustomerExceededFault
- ClusterAlreadyExistsFault
- ClusterNotFoundFault
- ClusterQuotaForCustomerExceededFault
- DefaultUserRequired
- DuplicateUserNameFault
- InsufficientClusterCapacityFault
- InvalidACLStateFault
- InvalidARNFault
- InvalidClusterStateFault
- InvalidCredentialsException
- InvalidKMSKeyFault
- InvalidMultiRegionClusterStateFault
- InvalidNodeStateFault
- InvalidParameterCombinationException
- InvalidParameterGroupStateFault
- InvalidParameterValueException
- InvalidSnapshotStateFault
- InvalidSubnet
- InvalidUserStateFault
- InvalidVPCNetworkStateFault
- MultiRegionClusterAlreadyExistsFault
- MultiRegionClusterNotFoundFault
- MultiRegionParameterGroupNotFoundFault
- NoOperationFault
- NodeQuotaForClusterExceededFault
- NodeQuotaForCustomerExceededFault
- ParameterGroupAlreadyExistsFault
- ParameterGroupNotFoundFault
- ParameterGroupQuotaExceededFault
- ReservedNodeAlreadyExistsFault
- ReservedNodeNotFoundFault
- ReservedNodeQuotaExceededFault
- ReservedNodesOfferingNotFoundFault
- ServiceLinkedRoleNotFoundFault
- ServiceUpdateNotFoundFault
- ShardNotFoundFault
- ShardsPerClusterQuotaExceededFault
- SnapshotAlreadyExistsFault
- SnapshotNotFoundFault
- SnapshotQuotaExceededFault
- SubnetGroupAlreadyExistsFault
- SubnetGroupInUseFault
- SubnetGroupNotFoundFault
- SubnetGroupQuotaExceededFault
- SubnetInUse
- SubnetNotAllowedFault
- SubnetQuotaExceededFault
- TagNotFoundFault
- TagQuotaPerResourceExceeded
- TestFailoverNotAvailableFault
- UserAlreadyExistsFault
- UserNotFoundFault
- UserQuotaExceededFault
Paginators#
Paginators are available on a client instance via the get_paginator method. For more detailed instructions and examples on the usage of paginators, see the paginators user guide.
The available paginators are: