Factor House

Once several teams share an MSK cluster, IAM policies can't answer the governance questions anymore. Now AI agents are getting access to Kafka too. On October 14 I'm walking through what governing a shared MSK cluster actually looks like: → Mapping teams to role-based access instead of writing IAM policies one principal at a time → Masking sensitive fields so engineers can troubleshoot production without seeing customer data → Approval workflows and audit trails for risky operations, whether a person or an AI agent runs them If you run MSK for more than one team, this one should help you spot the gaps in your setup. https://lnkd.in/gKVJesjY

If you're running Amazon MSK across multiple teams (or letting AI agents near it), IAM alone wont cut it. Chad Harris is sharing how to get access control, data masking and approval workflows right on October 14 👇 https://lnkd.in/g-EfMAz8

Operating Kafka on Amazon MSK with more than one team on the cluster? Join Chad Harris on October 14, he's an expert in this space, and has plenty of experience to share, don't miss it! 👇

Join my tech talk on Kafka production failures on June 10, 10am CET. I've spent years running Kafka at companies of every size. The failures I've seen rarely announce themselves. A subtle misconfiguration. A metric that looks fine until it doesn't. A consumer lag that spikes at 2am with no obvious cause. This session is about those moments: → Real production incidents → Debugging workflows that actually help → Observability signals worth paying attention to If you keep Kafka running in production, this one's for you. Register below. https://lnkd.in/gQ_j5MmD

If you're in Europe working with Kafka, don't miss this 👇 https://lnkd.in/gvesfzAM

Join Chad Harris, formerly of Block Inc., and Hugh Evans from Aiven for a live Kafka tech talk on June 10 at 10am CET. They'll discuss real-world operational failures, from subtle misconfigurations to full-scale incidents, and the debugging workflows that actually help 🧯