Create a Connect Cluster, create Connectors on it, and manage Connector lifecycle operations.
AutoMQ Connect uses two resource types. A Connect Cluster provides the Kafka Connect worker runtime and compute capacity. A Connector defines a source or sink data integration workload that runs on a Connect Cluster.Before creating a Connect Cluster, review Manage Plugins and identify the Managed or custom plugin version and Connector class that the workload requires. The selected plugin is installed on the Connect Cluster and is then available when you create a Connector.
Before you begin, prepare the following resources:
A running AutoMQ instance.
Kafka credentials with permissions for the topics and consumer groups that the Connector will use. For more information, see Manage Kafka ACLs.
The source or sink system and its access credentials.
A Kubernetes cluster, namespace, and ServiceAccount for the Connect Cluster workers. On AWS, bind the ServiceAccount to an IAM role that grants access to the Ops Bucket and any external AWS resources required by the plugin. For EKS preparation instructions, see Deploy to Amazon EKS.
Grant only the permissions required by the workload. A Sink Connector requires read permission for its Kafka topics and consumer group. A Source Connector requires write permission for its destination topics.
Open a Connector details page to view its status, tasks, metrics, and logs. You can update supported plugin properties and the task count, and you can perform the following lifecycle operations:
Pause: Stops data processing without deleting the Connector.
Resume: Resumes a paused Connector.
Restart: Restarts the Connector and its tasks to recover from an error or apply supported runtime changes.
Worker count, Worker Tier, Kubernetes placement, installed plugins, and Prometheus Remote Write settings belong to the Connect Cluster. Update those settings on the Connect Cluster rather than on an individual Connector.