No, you've got things reversed - as do most in this thread. Elastic's original announcement was disingenuous, they titled their blog post "Doubling Down on Ope

No, you've got things reversed - as do most in this thread. Elastic's original announcement was disingenuous, they titled their blog post "Doubling Down on Open" when they were making Elasticsearch and Kibana no longer open source. Furthermore, Elastic promised in the past that ALL FUTURE VERSIONS of the open core of Elasticsearch would remind Apache 2.0. They broke that promise when they switched to proprietary licenses only with 7.1.1. BTW, while the reasoning from Elastic is that they did it because of Amazon, the actual effect is just to make organizations like the one I work for (a non-profit that refuses to run proprietary software in prod) have to use one of these Apache 2.0 forks, while not stopping Amazon from operating their Elasticsearch service at all (since Amazon is always free to operate an Apache 2.0 service and indeed that's the whole damn point of the license)