My Projects

Official template for deploying the WarpStream Agents.

WarpStream Agents (Kafka without the disks)

warpstream-agents

Access key ID for the Cloudflare R2 bucket.

AWS secret access key for your cloudflare R2 storage bucket.

WarpStream agent pool name. Only needs to be changed if you're using a non-default virtual cluster ID: https://docs.warpstream.com/warpstream/background-information/agent-pools-and-virtual-clusters#running-a-warpstream-agent-with-a-non-default-agent-pool-or-virtual-cluster

WarpStream API obtained from the WarpStream admin console.

URL specifying which object store the WarpStream Agents will write/read to/from. We recommend Cloudflare R2 as documented here: https://docs.warpstream.com/warpstream/reference/use-the-agents-with-an-s3-compatible-object-store-minio-oracle-cloud-etc

WarpStream virtual cluster ID obtained from WarpStream admin console after signing up for a WarpStream account.

Hostname the WarpStream Agents will advertise in the Kafka protocol. This must be the Railway TCP proxy domain name generated by railway after the project is deployed. Can set a garbage value when first deploying as long as its updated later.

The port the WarpStream Agents will advertise in the Kafka protocol. This must be the port auto-generated by the Railway TCP proxy after creating the service. Can set a random value until then, but must be updated afterwards.

Whether the WarpStream Agents will enforce SASL authentication. Don't change this value otherwise your Kafka data will be exposed to the internet.