Thanks for sharing; I wrote the post and also submitted the distro to HN. In most cases (apparently per HN policy), blog posts that announce new services are removed in favor of direct links to the offering.

Is it really honest to say "Keeping Open Source Open"? Elasticsearch is 100% open source, even Apache Licensed, and you are implying that this is not the case "somehow". Sure "security" is missing, but who says that this has to be part of the open source project "Elasticsearch"?

Maybe it would be more honest to say "Forcing open source backing companies to avoid open core that is hated by AWS" ;) ?

(btw: I'm not associated with Elastic except loving their open source projects)

Ah, I probably did not correctly catch the news:

> Unfortunately, since June 2018, we have witnessed significant intermingling of proprietary code into the code base.

And you mean the x-pack stuff?

https://github.com/elastic/elasticsearch/blob/master/LICENSE...

Interesting, wasn't aware of it.