Module aws_sdk_memorydb::model

source ·
Expand description

Data structures used by operation inputs/outputs. Documentation on these types is copied from the model.

Modules

Structs

The status of the ACL update

An Access Control List. You can authenticate users with Access Contol Lists. ACLs enable you to control cluster access by grouping users. These Access control lists are designed as a way to organize access to clusters.

Returns the updates being applied to the ACL.

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).

Contains all of the attributes of a specific cluster.

A list of cluster configuration options.

A list of updates being applied to the cluster

Represents the information required for client programs to connect to the cluster and its nodes.

Provides details of the Redis engine version

Represents a single occurrence of something interesting within the system. Some examples of events are creating a cluster or adding or removing a node.

Used to streamline results of a search based on the property being filtered.

Represents an individual node within a cluster. Each node runs its own instance of the cluster's protocol-compliant caching software.

Describes an individual setting that controls some aspect of MemoryDB behavior.

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.

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.

A request to configure the number of replicas in a shard

Represents the output of a PurchaseReservedNodesOffering operation.

The offering type of this node.

The status of the online resharding

Represents a single security group and its status.

An update that you can apply to your MemoryDB clusters.

A request to apply a service update

Represents a collection of nodes in a cluster. One node in the node group is the read/write primary node. All the other nodes are read-only Replica nodes.

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

Represents the progress of an online resharding operation.

Represents a copy of an entire cluster as of the time when the snapshot was taken.

Represents the subnet associated with a cluster. This parameter refers to subnets defined in Amazon Virtual Private Cloud (Amazon VPC) and used with MemoryDB.

Represents the output of one of the following operations:

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

A cluster whose updates have failed

You create users and assign them specific permissions by using an access string. You assign the users to Access Control Lists aligned with a specific role (administrators, human resources) that are then deployed to one or more MemoryDB clusters.

Enums

When writing a match expression against AuthenticationType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
When writing a match expression against AzStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
When writing a match expression against DataTieringStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
When writing a match expression against InputAuthenticationType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
When writing a match expression against ServiceUpdateStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
When writing a match expression against ServiceUpdateType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
When writing a match expression against SourceType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.