This (while perhaps not perfect) is massive for us, it’s going to be especially useful for Kibana authentication to add readonly and write users, something we’ve wanted for a long time but haven’t been able to afford as a non-profit, charitable organisation. I know it’s not all 100% open source, but it’s better than a nginx reverse proxy hack or similar. Thank you Elastic for continuing to create fantastic software.
Security for Elasticsearch is now free
61–64 of 64 posts
Re: Security for Elasticsearch is now free
#62Too little too late? Trying to charge for TLS was a very poor move and it's made me not trust ElasticSearch...
Why don’t you want to pay for a feature that you need? The company that pays your wages makes money from selling something. Of course you sell what people need
TLS isn't like say, LDAP integration. One of those is a fancy enterprise feature you can totally charge for (and probably should), and one of those is a basic critical feature.
It would be unethical to charge $400/year to properly store user passwords as hashed instead of plaintext, wouldn't it?
Re: Security for Elasticsearch is now free
#63Earlier quoted context omitted.
Could you expand on the features that Open Distro misses and that Elastic offers?
You can see the OSS and Free offerings at https://www.elastic.co/subscriptions . Real question is what are the Open Distro is offering: * Alerting - you can use ElasticAlert * Security - Search Guard * SQL - https://github.com/NLPchina/elasticsearch-sql There very little reason (IMO) for users to a choose "Open Distro" except that it comes as an AWS image.
Basically same debate as between Linux From Scratch and a full-featured distro such as Ubuntu.
Re: Security for Elasticsearch is now free
#64Running Elasticsearch on K8s storing 16TB of compressed logs across 6 data nodes and ~4600 shards. We're a really happy ES customer. We've on ESv6 at the moment and it's been running amazingly for us. We've halved our storage and running costs by moving from 5 to 6. We've always been a licensed customer and they are in front of AWS with their features (we run our k8s stack on AWS though :) )
That's an insane number of shards, you should be closer to 500 for that amount of data and only 6 nodes.