Shifting kafka workloads to public cloud platforms seems like a common-sense economics, as cloud empowers companies to scale resources as needed and keeps your Kafka high available. You only pay for what you use, thus saving money. Right? Well, not necessarily. Unless you are vigilant and relentless in monitoring, cloud spend can surprise you in unexpected ways through ingress/ egress fees, over provisioning, forgetting to turn off unwanted resources, not picking the right combination of instances, and so on, can quickly make costs go out of control. But public cloud cost optimization does not have to be esoteric or a long arduous road. Needless to say, achieving high availability for Kafka on cloud is both time consuming and expensive, costing a leg and arm, requiring a dedicated team to handle the entire infrastructure. I would like to share the lessons learnt from the field, productionizing cloud based kafka clusters at many enterprise companies which cover topics like techniques to optimize Kafka’s network transfer costs, configuring production & consumption to single & MZ zone, compression tools, tuning the fan-out etc. So In this session let us discuss ways and means to demystify and explore methods to potentially reduce your cloud spend on KAFKA clusters