Module aws_sdk_dax::types

source ·
Expand description

Data structures used by operation inputs/outputs.

Modules§

  • builders
    Builders
  • error
    Error types that Amazon DynamoDB Accelerator (DAX) can respond with.

Structs§

  • Cluster

    Contains all of the attributes of a specific DAX cluster.

  • Endpoint

    Represents the information required for client programs to connect to the endpoint for a DAX cluster.

  • Event

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

  • Node

    Represents an individual node within a DAX cluster.

  • NodeTypeSpecificValue

    Represents a parameter value that is applicable to a particular node type.

  • NotificationConfiguration

    Describes a notification topic and its status. Notification topics are used for publishing DAX events to subscribers using Amazon Simple Notification Service (SNS).

  • Parameter

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

  • ParameterGroup

    A named set of parameters that are applied to all of the nodes in a DAX cluster.

  • ParameterGroupStatus

    The status of a parameter group.

  • ParameterNameValue

    An individual DAX parameter.

  • SecurityGroupMembership

    An individual VPC security group and its status.

  • SseDescription

    The description of the server-side encryption status on the specified DAX cluster.

  • SseSpecification

    Represents the settings used to enable server-side encryption.

  • Subnet

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

  • SubnetGroup

    Represents the output of one of the following actions:

  • Tag

    A description of a tag. Every tag is a key-value pair. You can add up to 50 tags to a single DAX cluster.

Enums§

  • ChangeType
    When writing a match expression against ChangeType, 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.
  • ClusterEndpointEncryptionType
    When writing a match expression against ClusterEndpointEncryptionType, 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.
  • IsModifiable
    When writing a match expression against IsModifiable, 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.
  • ParameterType
    When writing a match expression against ParameterType, 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.
  • SourceType
    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.
  • SseStatus
    When writing a match expression against SseStatus, 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.