Module aws_sdk_kafka::types 
source · Expand description
Data structures used by operation inputs/outputs.
Modules
- Builders
- Error types that Managed Streaming for Kafka can respond with.
Structs
- Specifies the EBS volume upgrade information. The broker identifier must be set to the keyword ALL. This means the changes apply to all the brokers in the cluster. 
- Describes the setup to be used for Apache Kafka broker nodes in the cluster. 
- BrokerNodeInfo 
- Information about the current software installed on the cluster. 
- Includes all client authentication information. 
- Returns information about a cluster. 
- Returns information about a cluster. 
- Returns information about a cluster operation. 
- Step taken during a cluster operation. 
- State information about the operation step. 
- Contains source Apache Kafka versions and compatible target Apache Kafka versions. 
- Represents an MSK Configuration. 
- Specifies the configuration to use for the brokers. 
- Describes a configuration revision. 
- Information about the broker access configuration. 
- Contains information about the EBS storage volumes attached to Apache Kafka broker nodes. 
- The data-volume encryption details. 
- The settings for encrypting data in transit. 
- Includes encryption-related information, such as the AWS KMS key used for encrypting data at rest and whether you want MSK to encrypt your data in transit. 
- Returns information about an error state of the cluster. 
- Details for IAM access control. 
- Indicates whether you want to turn on or turn off the JMX Exporter. 
- Indicates whether you want to turn on or turn off the JMX Exporter. 
- Information about cluster attributes that can be updated via update APIs. 
- Indicates whether you want to turn on or turn off the Node Exporter. 
- Indicates whether you want to turn on or turn off the Node Exporter. 
- The node information object. 
- JMX and Node monitoring for the MSK cluster. 
- JMX and Node monitoring for the MSK cluster. 
- Prometheus settings. 
- Prometheus settings. 
- Provisioned cluster. 
- Provisioned cluster request. 
- Contains information about provisioned throughput for EBS storage volumes attached to kafka broker nodes. 
- Public access control for brokers.
- Details for client authentication using SASL. 
- Details for SASL/SCRAM client authentication. 
- Serverless cluster. 
- Includes all client authentication information. 
- Serverless cluster request. 
- Details for client authentication using SASL. 
- Contains information about storage volumes attached to MSK broker nodes. 
- Details for client authentication using TLS. 
- Error info for scram secret associate/disassociate failure. 
- The configuration of the Amazon VPCs for the cluster. 
- Zookeeper node information. 
Enums
- When writing a match expression againstBrokerAzDistribution, 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 againstClientBroker, 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 againstClusterState, 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 againstClusterType, 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 againstConfigurationState, 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 againstEnhancedMonitoring, 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 againstKafkaVersionStatus, 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 againstNodeType, 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 againstStorageMode, 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.