Amazon responds to Elastic’s change to its open source software license

In response to Elastic changes its license for Elasticsearch and Kibana products, Amazon responded with plans to create and maintain an Apache License, Version 2.0 fork of open source products.

Elastic announced earlier this week that it will be moving from the Apache 2.0 license to a dual license for Elasticsearch and Kibana, which includes the Elastic license and the server-side public license (SSPL). “We believe Amazon’s behavior is inconsistent with the norms and values ​​that are particularly important in the open source ecosystem. Our hope is to take our presence in the market and use it to address this now so that others don’t face the same issues in the future,” explained Shay Banon, Founder and CEO of Elastic. , in one Publish.

Amazon now argues that this means Elasticsearch and Kibana will no longer be open source and that the Elastic license limits how the code can be used while the server-side public license makes it unacceptable to the open source community.

“Elastic’s claims that the SSPL is ‘free and open’ are misleading and misleading. They try to claim the benefits of open source, while undermining the very definition of open source itself. Their choice of SSPL belies this. SSPL is a non-open source license designed to look like an open source license, blurring the lines between the two,” the Amazon Elasticsearch team wrote in a blog post. “Most people are not fooled. We didn’t make them do anything. They believe that restricting their license will prevent others from offering managed Elasticsearch services, which will allow Elastic to grow a bigger business. Elastic has the right to change its license, but it must also step in and make its own decision. »

Banon argues that Amazon confused the community when it decided to launch its Elasticsearch-based service and call it Amazon Elasticsearch Service. He also states that Amazon misled the community by saying that the service was developed in conjunction with Elastic when it was not, and that it used third-party code from Elastic’s commercial code as a port. from the Open Distro project. “We expect a few of our competitors to try to spread all sorts of FUD around this change. Let me be clear to any naysayers. We strongly believe in the principles of free and open products, and transparency with the community. Our track record is a testament to this commitment, and we will continue to build on it,” Banon said. Explain.

Amazon forks of Elasticsearch and Kibana will be based on the latest ALv2 licensed codebases, version 7.10, and new GitHub repositories will be released over the next few weeks, Amazon explained. Amazon Elasticsearch Service will also be powered by the new forks and the company will provide new features, fixes and improvements. The team explained that the change should have no negative impact on their current service. “This change will not slow the speed of improvements we deliver to our customers. On the contrary, a community-owned Elasticsearch codebase gives us new opportunities to make faster progress in improving stability, scalability, resiliency, and performance,” the team wrote. “We look forward to providing a truly open source option for Elasticsearch and Kibana using the ALv2 license, and building and supporting that future with the community.”