Module aws_sdk_mq::types

source ·
Expand description

Data structures used by operation inputs/outputs.

Modules

Structs

  • The action required to resolve a broker issue when the broker is in a CRITICAL_ACTION_REQUIRED state.

  • Name of the availability zone.

  • Types of broker engines.

  • Returns information about all brokers.

  • Option for host instance type.

  • Returns information about all brokers.

  • Returns information about all configurations.

  • A list of information about the configuration.

  • Returns information about the specified configuration revision.

  • Broker configuration information

  • Id of the engine version.

  • Optional. The metadata of the LDAP server used to authenticate and authorize connections to the broker.

  • Optional. The metadata of the LDAP server used to authenticate and authorize connections to the broker.

  • The list of information about logs to be enabled for the specified broker.

  • The list of information about logs currently enabled and pending to be deployed for the specified broker.

  • The list of information about logs to be enabled for the specified broker.

  • Returns information about the XML element or attribute that was sanitized in the configuration.

  • A user associated with the broker. For RabbitMQ brokers, one and only one administrative user is accepted and created when a broker is first provisioned. All subsequent broker users are created by making RabbitMQ API calls directly to brokers or via the RabbitMQ web console.

  • Returns information about the status of the changes pending for the ActiveMQ user.

  • Returns a list of all broker users. Does not apply to RabbitMQ brokers.

  • The scheduled time period relative to UTC during which Amazon MQ begins to apply pending updates or patches to the broker.

Enums

  • When writing a match expression against AuthenticationStrategy, 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 BrokerState, 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 BrokerStorageType, 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 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.
  • When writing a match expression against DayOfWeek, 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 DeploymentMode, 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 EngineType, 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 SanitizationWarningReason, 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.