Changes from an external database must be published to Kafka topics.
Run Kafka Connect connectors with MSK without operating a custom EC2 worker cluster.
Which configuration is most appropriate?
Run a source connector with Amazon MSK Connect and publish the changes to MSK topics.
Detailed explanation
MSK Connect manages Kafka Connect workers and can ingest external-system data into MSK topics.
MSK Connect manages Kafka Connect workers and can ingest external-system data into MSK topics.
Glacier is archival storage and is not a low-latency Kafka source connector.
Glacier is archival storage and is not a low-latency Kafka source connector.
Macie detects sensitive data in S3 and does not run Kafka Connect connectors.
Macie detects sensitive data in S3 and does not run Kafka Connect connectors.
CloudFormation provisions resources but does not collect external database changes.
CloudFormation provisions resources but does not collect external database changes.
Check official documentation
Compare the following points with the official documentation.
Amazon MSK Connectのコネクタ、ワーカー、ソースコネクタの公式説明を確認する。
What to confirm
Kafkaブローカー、コネクタ実行基盤、アーカイブ・監査サービスの役割を区別できる。
Key points
- MSK Connect
- Kafka Connect
- Source connector
- External database
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Connector versus broker
The connector performs external I/O; MSK brokers retain and distribute topic records.
Managed workers
Worker capacity, plugins, network paths, and credentials still require operational monitoring.