Tenderd: a Control Tower-governed, region-locked AWS landing zone in the UAE

An AI fleet-analytics platform lives on its event streams: telemetry from vehicles and heavy equipment feeds the models, dashboards, and alerts customers pay for. Tenderd’s streaming layer had to cross clouds without breaking the Kafka ecosystem the platform was built on — producers, consumers, and Confluent connectivity all expecting Kafka semantics — and land in a form the small platform team could operate across four delivery environments without becoming broker administrators. Re-writing the streaming layer to a different technology mid-migration was the risk to avoid; running self-managed Kafka on AWS was the toil to avoid.

VeUP’s architecture takes the third path: Amazon MSK as the managed Kafka streaming layer, giving the platform wire-compatible Kafka — existing producers, consumers, and Confluent connectivity carry over — with brokers, patching, and failure recovery handled by the service. The streams feed the platform’s IoT data-processing components and the analytics tier, where Amazon Redshift serves as the log and analytics warehouse; the application plane around the streams runs on Amazon ECS Fargate with EventBridge-driven scheduling; and bulk data moves from GCP Cloud Storage into Amazon S3 via AWS DataSync, with MongoDB Atlas production data syncing continuously ahead of cutover. Like the rest of the estate, the MSK clusters are Terraform-provisioned per delivery environment — dev through production — so the streaming layer’s configuration is versioned, reviewed, and identical wherever it runs, with the production migration sequenced to Middle East region availability.