Enterprise

‘It’s not OK’: Elastic takes aim at AWS, at the risk of major collateral damage

Elastic's long-running dispute with AWS entered a new chapter last week with big changes to two of its open-source projects. AWS now plans to take those projects under its wing.

‘It’s not OK’: Elastic takes aim at AWS, at the risk of major collateral damage

"I don't know why this is surprising to people," Elastic CEO Shay Banon said in an interview with Protocol.

Photo: Michael Nagle/Getty Images

Fed up with what he sees as unfair competition from AWS, Elastic CEO Shay Banon felt he had no choice but to restrict the way third parties can use two important open-source projects developed by his company. Yet much of enterprise tech thinks he just threw the baby out with the bathwater.

Last Thursday, Elastic published a blog post — curiously titled "Doubling down on open, Part II" — announcing that Elasticsearch and Kibana, two widely used open-source projects in enterprise tech, would no longer be available under the permissive Apache 2.0 license. Instead, all subsequent releases to those projects will only be available under either a controversial new license known as the SSPL, or the Elastic License, both of which were designed to make it difficult for cloud companies to sell managed versions of the open-source projects they're applied to.

Elastic has never tried to hide its disdain for AWS, a feud that dates back to the 2015 launch of Amazon Elasticsearch Service. The introduction of that AWS service, a managed version of the Elasticsearch open-source project, was arguably the low point in the strained history between enterprise tech companies based around open-source projects and AWS.

It is, of course, completely legal for AWS — or any company — to build its own service around any permissively licensed open-source project. In fact, AWS reacted to Elastic's decision Thursday afternoon by announcing plans to fork the two projects, or to take them in a new AWS-led direction, under the same permissive Apache 2.0 license.

But a generation of open-source enterprise companies (and their venture capitalist backers) see AWS as an anticompetitive gorilla stomping on their opportunity to monetize innovative software, and Elastic took particular offense to AWS' use of the Elasticsearch trademark.

"I don't know why this is surprising to people," Banon said in an interview with Protocol. "I'm making a stand here. I'm drawing a line and saying this is not OK."

However, critics argued Banon's decision paved the way for Amazon to turn its open-source distribution of the Elasticsearch project, the Open Distro for Elasticsearch, into a proper fork. The move had enormous potential to disappoint contributors to the Elasticsearch and Kibana projects who expected their work would be freely available to the community, only for that promise to be discarded once it was no longer economically comfortable for its corporate backer.

"Choosing to fork a project is not a decision to be taken lightly, but it can be the right path forward when the needs of a community diverge — as they have here. An important benefit of open-source software is that when something like this happens, developers already have all the rights they need to pick up the work themselves, if they are sufficiently motivated," AWS said in the post announcing its decision.

After AWS published its decision, Banon issued an additional statement: "When we announced the change, we sadly expected this. This what made it so hard. But I am also relieved. Relieved we are free to focus on products vs. battle abuse. Relieved that I can trust our community will see through this misinformation & confusion."

While legal experts believe Banon has a solid trademark case against AWS, the licensing changes clearly did not deter AWS, and they have no effect on companies like Microsoft and Google Cloud, which have signed deals with Elastic.

"They are aiming to hit Amazon, but what they are doing is throwing a boulder at Amazon floating peacefully in a pond of an ecosystem," said VM (Vicky) Brasseur, a corporate strategist and former vice president of the Open Source Initiative. "I don't think it's worth it. They are going to destroy their ecosystem."

Quite a stretch

Elasticsearch is an open-source search engine first released in 2010 by Banon, who would go on to co-found Elastic in 2012. It is often used alongside two other Elastic open-source projects, Logstash and Kibana, to form the "ELK stack," which is well known in enterprise tech circles among companies that want to build search capabilities for their websites while also using those search capabilities to pursue their system logs for events such as errors.

Customers can buy a managed version of this stack called Elastic Cloud, which runs on all three major U.S. cloud providers, or manage it themselves on either their own hardware or clouds. But there are also some companies and individual users that are happy to take on the burden of managing the open-source version.

The new licensing changes, however, mean that companies using this open-source version must now agree that they won't use Elasticsearch and Kibana as part of their own cloud service, and that has raised questions. The changes are directed at big cloud providers, but there are many small and medium businesses that could be using the open-source projects as part of their own software stack in a way that may or may not be infringing on the new licenses, depending on the quality of the lawyers involved in any dispute.

"If you're using them, please look at how they fit into your software supply chain, look at how this is going to impact your product and your projects. Don't just overlook it and assume it's nothing," Brasseur said.

Banon said "the vast majority" of Elasticsearch and Kibana users will not be affected by these licensing changes, but he acknowledged there will be valid concerns felt inside the Elasticsearch community.

"I'm very worried about [alienating community members]; this is why we didn't make this change lightly," Banon said. "Regardless of how much we try to relax our user base, some people will end up being alienated, and others, which I'm more worried about, might be fed by FUD," the tried-and-true "fear, uncertainty and doubt" campaigns that have been part of enterprise tech marketing for decades.

Brasseur agreed that the licensing move comes with significant risks to Elastic's goodwill inside its community of contributors.

"They're now taking these contributions, which were given by external contributors freely and openly with the assumption that their contributions would be freely and openly available, and now they're locking them up behind a non-open license," she said. "It's perfectly fine to do that. But you better be talking to your community up front and telling them how and why, and then I think it's probably wise for you to be then compensating people for the value that they have provided to your company. Otherwise, you're just using them."

Off the mark

The root cause of the dispute between Elastic and AWS mostly centers on the trademark issue, which prompted a lawsuit from Elastic in 2019 that continues to work its way through the court system.

The use of that trademark caused a great deal of confusion among Elastic's customers, according to Banon, who believed that the AWS service was the result of collaboration between the two companies when it was really just a repackaging of the open-source Elasticsearch project. A tweet from Amazon CTO Werner Vogels calling the new service a "partnership" certainly did not help.

"To modify Elastic's product and call it Amazon Elasticsearch is, in my view, a pretty clear trademark infringement," said Pamela Chestek, a trademark attorney and former intellectual property attorney at IBM's Red Hat.

But when AWS launched the Open Distro for Elasticsearch in 2019, the trademark dispute also turned into a dispute over code.

AWS charged that Elastic was co-mingling open-source code with proprietary code, making it hard for users to know if they required a paid subscription or not to use certain features. The Open Distro was pitched as a way to get the benefits of open-source Elasticsearch with the features needed to make it work properly, and it was released under the Apache 2.0 license.

Elastic denied that it was trying to confuse its users, and alleged that AWS was using third-party code in that distribution that was a copy of its own work.

"Recently, we found more examples of what we consider to be ethically challenged behavior. We have differentiated with proprietary features, and now we see these feature designs serving as 'inspiration' for Amazon, telling us their behavior continues and is more brazen," Banon said in a blog post Tuesday.

License to print money

As with all disputes in enterprise software, this one really comes down to money. Elastic doesn't make money when people use the open-source versions of its software, and all things considered, would prefer they pay for the licensed versions.

From the outside it's hard to pinpoint exactly how much money AWS has made from its Elasticsearch services, but it's a non-zero amount: AWS likely recorded more than $12 billion in overall cloud revenue during the fourth quarter of 2020. At the same time, Elastic's own cloud services are growing quite strongly as the world shifts to cloud-based software.

Elastic revenue rose 43% in its most recent quarter, with SaaS subscription revenue for Elastic Cloud driving much of that growth. Over the course of 2020, Banon wasn't worried enough about the competitive threat from AWS to mention it during the quarterly conversations with the financial community.

In fact, in answering a question about competition with the cloud providers from a financial analyst during Elastic's December earnings conference, Banon said: "We feel like we're ahead of the pack on all three when it comes to the maturity and the future readiness of our products, and that's reflected, I think, by the usage of it." Elastic's stock has more than doubled in the last 12 months.

"We're doing well as a business, and I'm not going to sit here and apologize for it," Banon said. "It's not about doing well or not doing well as a business, it's about doing what's right."

In the aftermath of the licensing changes, however, what's "right" for Elasticsearch users, open-source contributors, and Elastic shareholders takes on different meanings, depending on where you sit.

"I would have been a lot more sympathetic to Elastic if they said, 'look, these choices we made when we were very young, they aren't working out for us anymore. They aren't working out with our business plan,'" Chestek said. "A lot of people would be unhappy with that, but it would be honest."

Update: This article was updated at 3:45 p.m. PT to include a statement from Elastic following the release of AWS' blog post.

LA is a growing tech hub. But not everyone may fit.

LA has a housing crisis similar to Silicon Valley’s. And single-family-zoning laws are mostly to blame.

As the number of tech companies in the region grows, so does the number of tech workers, whose high salaries put them at an advantage in both LA's renting and buying markets.

Photo: Nat Rubio-Licht/Protocol

LA’s tech scene is on the rise. The number of unicorn companies in Los Angeles is growing, and the city has become the third-largest startup ecosystem nationally behind the Bay Area and New York with more than 4,000 VC-backed startups in industries ranging from aerospace to creators. As the number of tech companies in the region grows, so does the number of tech workers. The city is quickly becoming more and more like Silicon Valley — a new startup and a dozen tech workers on every corner and companies like Google, Netflix, and Twitter setting up offices there.

But with growth comes growing pains. Los Angeles, especially the burgeoning Silicon Beach area — which includes Santa Monica, Venice, and Marina del Rey — shares something in common with its namesake Silicon Valley: a severe lack of housing.

Keep Reading Show less
Nat Rubio-Licht

Nat Rubio-Licht is a Los Angeles-based news writer at Protocol. They graduated from Syracuse University with a degree in newspaper and online journalism in May 2020. Prior to joining the team, they worked at the Los Angeles Business Journal as a technology and aerospace reporter.

While there remains debate among economists about whether we are officially in a full-blown recession, the signs are certainly there. Like most executives right now, the outlook concerns me.

In any case, businesses aren’t waiting for the official pronouncement. They’re already bracing for impact as U.S. inflation and interest rates soar. Inflation peaked at 9.1% in June 2022 — the highest increase since November 1981 — and the Federal Reserve is targeting an interest rate of 3% by the end of this year.

Keep Reading Show less
Nancy Sansom

Nancy Sansom is the Chief Marketing Officer for Versapay, the leader in Collaborative AR. In this role, she leads marketing, demand generation, product marketing, partner marketing, events, brand, content marketing and communications. She has more than 20 years of experience running successful product and marketing organizations in high-growth software companies focused on HCM and financial technology. Prior to joining Versapay, Nancy served on the senior leadership teams at PlanSource, Benefitfocus and PeopleMatter.

Policy

SFPD can now surveil a private camera network funded by Ripple chair

The San Francisco Board of Supervisors approved a policy that the ACLU and EFF argue will further criminalize marginalized groups.

SFPD will be able to temporarily tap into private surveillance networks in certain circumstances.

Photo: Justin Sullivan/Getty Images

Ripple chairman and co-founder Chris Larsen has been funding a network of security cameras throughout San Francisco for a decade. Now, the city has given its police department the green light to monitor the feeds from those cameras — and any other private surveillance devices in the city — in real time, whether or not a crime has been committed.

This week, San Francisco’s Board of Supervisors approved a controversial plan to allow SFPD to temporarily tap into private surveillance networks during life-threatening emergencies, large events, and in the course of criminal investigations, including investigations of misdemeanors. The decision came despite fervent opposition from groups, including the ACLU of Northern California and the Electronic Frontier Foundation, which say the police department’s new authority will be misused against protesters and marginalized groups in a city that has been a bastion for both.

Keep Reading Show less
Issie Lapowsky

Issie Lapowsky ( @issielapowsky) is Protocol's chief correspondent, covering the intersection of technology, politics, and national affairs. She also oversees Protocol's fellowship program. Previously, she was a senior writer at Wired, where she covered the 2016 election and the Facebook beat in its aftermath. Prior to that, Issie worked as a staff writer for Inc. magazine, writing about small business and entrepreneurship. She has also worked as an on-air contributor for CBS News and taught a graduate-level course at New York University's Center for Publishing on how tech giants have affected publishing.

Enterprise

These two AWS vets think they can finally solve enterprise blockchain

Vendia, founded by Tim Wagner and Shruthi Rao, wants to help companies build real-time, decentralized data applications. Its product allows enterprises to more easily share code and data across clouds, regions, companies, accounts, and technology stacks.

“We have this thesis here: Cloud was always the missing ingredient in blockchain, and Vendia added it in,” Wagner (right) told Protocol of his and Shruthi Rao's company.

Photo: Vendia

The promise of an enterprise blockchain was not lost on CIOs — the idea that a database or an API could keep corporate data consistent with their business partners, be it their upstream supply chains, downstream logistics, or financial partners.

But while it was one of the most anticipated and hyped technologies in recent memory, blockchain also has been one of the most failed technologies in terms of enterprise pilots and implementations, according to Vendia CEO Tim Wagner.

Keep Reading Show less
Donna Goodison

Donna Goodison (@dgoodison) is Protocol's senior reporter focusing on enterprise infrastructure technology, from the 'Big 3' cloud computing providers to data centers. She previously covered the public cloud at CRN after 15 years as a business reporter for the Boston Herald. Based in Massachusetts, she also has worked as a Boston Globe freelancer, business reporter at the Boston Business Journal and real estate reporter at Banker & Tradesman after toiling at weekly newspapers.

Fintech

Kraken's CEO got tired of being in finance

Jesse Powell tells Protocol the bureaucratic obligations of running a financial services business contributed to his decision to step back from his role as CEO of one of the world’s largest crypto exchanges.

Photo: David Paul Morris/Bloomberg via Getty Images

Kraken is going through a major leadership change after what has been a tough year for the crypto powerhouse, and for departing CEO Jesse Powell.

The crypto market is still struggling to recover from a major crash, although Kraken appears to have navigated the crisis better than other rivals. Despite his exchange’s apparent success, Powell found himself in the hot seat over allegations published in The New York Times that he made insensitive comments on gender and race that sparked heated conversations within the company.

Keep Reading Show less
Benjamin Pimentel

Benjamin Pimentel ( @benpimentel) covers crypto and fintech from San Francisco. He has reported on many of the biggest tech stories over the past 20 years for the San Francisco Chronicle, Dow Jones MarketWatch and Business Insider, from the dot-com crash, the rise of cloud computing, social networking and AI to the impact of the Great Recession and the COVID crisis on Silicon Valley and beyond. He can be reached at bpimentel@protocol.com or via Google Voice at (925) 307-9342.

Latest Stories
Bulletins