MotherDuck provides cloud-based, serverless access to DuckDB
There is no direct connection to MotherDuck from any Apache Kafka-compliant service. However, it can be done with an orchestration tool like Estuary. This guide will rely on our Estuary integration guide and point out what you'll need from MotherDuck to make it all work.
Please review all the steps available for our Estuary integration first.
Have a MotherDuck account and sign in.
WarpStream account - get access to WarpStream by registering here.
A WarpStream cluster is up and running with a populated topic.
In MotherDuck, navigate to "General" under "Settings" and select "+ Create token." Give it a name and then save it. You will need this in Estuary later.
Obtain the Bootstrap Broker from the WarpStream console by navigating to your cluster and clicking the Connect tab. If you don't have SASL credentials, you can also create a set of credentials from the console.
Save these values along with your MotherDuck access token for Estuary.
In Estuary, configure a Destination by selecting it from the navigation dashboard and then clicking on "+ NEW MATERIALIZATION."
Find and select the MotherDuck connector:
In step 2 below, the first item will be the access token created in MotherDuck. Next will be the database in MotherDuck to create the tables; this should already exist. Estuary needs to stage the data load on AWS S3, so you must define an S3 Staging Bucket, Access Key ID, Secret Access Key, and the S3 Bucket Region for Estuary to utilize.
Finish your Estuary setup process, and then once your Topics sync to MotherDuck, which is quick, they will display as tables in the database.
Congratulations! You are now able to pipe your WarpStream topics into MotherDuck via Estuary.
Next, check out the WarpStream docs for configuring the WarpStream Agent, or review the Estuary docs and MotherDuck docs to learn more about what is possible with WarpStream, MotherDuck, and Estuary!
Last updated
Was this helpful?
Was this helpful?
