Sophos adopts Bring Your Own Cloud from Aiven
Initially, the Aiven for Kafka service was deployed on Aiven-managed infrastructure on AWS. In this arrangement, Sophos was not able to apply discounted pricing from AWS to Kafka.
Sophos looked into the Aiven’s BYOC model on AWS as a way of reducing its Kafka-related costs without sacrificing performance or scalability. With this model, Aiven would continue to manage Kafka, but importantly the clusters would run on cloud infrastructure within Sophos’s AWS account. This would allow Sophos to apply its AWS compute savings plans to the Aiven service.
Sophos began its BYOC migration on AWS with proofs of concept and testing before transitioning to live migration. Aiven's self-service automation for AWS BYOC streamlined the process, enabling a rapid and successful migration.
“We migrated all 79 Kafka clusters with BYOC, including some very large instances, across the nine AWS regions with zero downtime and zero data loss. And we did it in a single month, rather than the four months we’d anticipated,” says Campbell.
“Data loss is unacceptable in our business. If we had seen any data loss or downtime from the migration, it would have compromised our ability to safeguard our customers. Instead, all of them remain protected at every stage of the BYOC AWS migration.”