- ‣ Google's cloud business lost over $ 5.5 billion last year
- ‣ Microsoft Azure Functions Vulnerable to Docker Escape Bug
- ‣ Pinecone, a serverless vector database for machine learning, leaves stealth with $10M funding
- ‣ Researchers detect new malware targeting Kubernetes clusters to mine Monero
- ‣ GitLab Changes its Pricing Plan; Drops Starter Tier
- ‣ Microsoft Security Business Surpasses $10 Billion in Revenue
- ‣ Researchers uncover a 10-year old vulnerability in Linux
- ‣ IBM Introduces New Cloud Pricing
- ‣ AWS to offer free eight-week training
- ‣ IBM acquires cloud consultancy firm - Taos Mountain
- ‣ Driftctl: A Tool to detect Infrastructure Drifts
- ‣ New Work From Home Expansion From OpsRamp Network.
- ‣ AWS announces forks of Elasticsearch and Kibana
- ‣ CockroachLabs Secures $160M to Grow Their Distributed SQL Database
- ‣ AWS Unveils The New ML-Powered Amazon DevOps Guru
- ‣ Grafana Adds A Free Tier To Its Cloud Observability Platform
- ‣ Sysdig Report Says 58% Of Container Images Run As Root
AWS announces forks of Elasticsearch and Kibana
Jan. 26, 2021, 11:48 p.m. in Cloud Computing
AWS will step up to create and maintain a ALv2-licensed fork of open source Elasticsearch and Kibana
Making a targeted change to how we license our source code.
Some of our users might be alienated.
This change won’t affect the vast majority of users.
It will restrict cloud service providers from offering our software as a service.
On the 14th of January 2021, the CEO of Elastic, makers of Elasticsearch, an open-source search and analytic engine and its accompanying data visualization dashboard Kibana, Shay Banon, announced via an official blog-post that they were enforcing more restrictive licensing on the programs; moving them from their open-source codes from Apache 2.0 license programs to an SSPL (Server Side Public License) and Elastic License.
The company claimed they took this move to prevent companies such as AWS (Amazon web services') from using their products and search engines and providing them as services to consumers without doing business with them first and that this affected product growth as this prevented them from receiving funds that would have gone into improving the product.
The company, in their official announcement, said, “With the shift to SaaS as a delivery model, some cloud service providers have taken advantage of open source products by providing them as a service, without contributing back. This diverts funds that would have been reinvested into the product and hurt users and the community.
After the initial announcement, many suspected that this move had something to do with AWS, seeing as the two companies have had a strained relationship since 2015 alongside a lawsuit in 2019. In a follow-up post, the company confirmed these suspicions saying, “So why the change? AWS and Amazon Elasticsearch Service. They have been doing things that we think are just NOT OK since 2015, and it has only gotten worse. If we don't stand up to them now, as a successful company and leader in the market, who will?"
Exactly a week after this announcement, Amazon Web Services’ also made an announcement. In this announcement, the company announced that in light of the new restrictive license placed on ElasticSearch and Kibana, the company would show its commitment to open-source programs by launching new forks of the programs using the previous licensing, Apache 2.0. , a move that is within their legal rights.
The announcement made on the AWS blog states, “In order to ensure open source versions of both packages remain available and well supported, including in our own offerings, we are announcing today that AWS will step up to create and maintain an ALv2-licensed fork of open source Elasticsearch and Kibana.”
In the announcement, the company said they were fully committed to maintaining the new open-source projects themselves and were well equipped to do so. They also used the statement to dispute the claims that they move by Elastic was forced by AWS and maintained that they were working with the company the entire them and denied any claims that they were making any fork of the project before the announcement by Elastic.
“All changes to Elasticsearch were sent as upstream pull requests, and we then included the “oss” builds offered by Elastic in our distribution. This ensured that we were collaborating with the upstream developers and maintainers, and not creating a “fork” of the software.”
While some members of the open-source community agree with the move made by Elastic to protect and monetize their advanced software, there are many who disagree and also say that Elastic played into the hands of AWS and provided them an opportunity to fully work on forking the software.
Following the announcement by AWS, the CEO of Elastic took to Twitter, saying he expected AWS to fork the software and said it was what made the decision a tough one to take.
Regardless of the shots thrown by both companies, it is left to be seen which of these companies would pull in the most ElasticSearch users.