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§
Details of an Amazon MSK Cluster.
Information regarding UpdateBrokerCount.
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.
The client VPC connection object.
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.
Returns information about a cluster operation.
Returns information about a provisioned cluster operation.
Returns information about a serverless cluster operation.
Returns information about a cluster operation.
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.
Details about consumer group replication.
Details about consumer group replication.
Controller node information.
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 Kafka Cluster to be used as source / target for replication.
Details of an Amazon VPC which has network connectivity to the Apache Kafka cluster.
Information about Kafka Cluster used as source / target for replication.
Summarized information about Kafka Cluster used as source / target for replication.
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.
Specifies configuration for replication between a source and target Kafka cluster.
Specifies configuration for replication between a source and target Kafka cluster (sourceKafkaClusterAlias -> targetKafkaClusterAlias)
Summarized information of replication between clusters.
Configuration for specifying the position in the topics to start replicating from.
- Details about the state of a replicator
Information about a replicator.
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.
Details about topic replication.
Details for updating the topic replication of a replicator.
Error info for scram secret associate/disassociate failure.
Description of the requester that calls the API operation.
The configuration of the Amazon VPCs for the cluster.
The VPC connection object.
Description of the VPC connection.
- Description of the VPC connection.
- VPC connectivity access control for brokers.
Includes all client authentication information for VPC connectivity.
Details for IAM access control for VPC connectivity.
Details for SASL client authentication for VPC connectivity.
Details for SASL/SCRAM client authentication for VPC connectivity.
Details for TLS client authentication for VPC connectivity.
Zookeeper node information.
Enums§
- When writing a match expression against
BrokerAzDistribution
, 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
ClientBroker
, 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
ClusterState
, 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
ClusterType
, 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
ConfigurationState
, 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
CustomerActionStatus
, 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
EnhancedMonitoring
, 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
KafkaVersionStatus
, 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
NodeType
, 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
ReplicationStartingPositionType
, 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
ReplicatorState
, 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
StorageMode
, 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
TargetCompressionType
, 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
UserIdentityType
, 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
VpcConnectionState
, 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.