I kept feeling like I was reading the same thing over and over and just not finding out what exactly Amazon is doing now that it won't be able to do in the future. Skimming the links to the blog post and FAQ didn't help much.
Whatever it is it's pretty deep in the weeds. It looks like the intent is for most users to be unaffected; non-AWS cloud providers to be unaffected; even AWS's Elastic Cloud to be unaffected; but AWS has to stop doing something with specific regard to Elastic Search and I can't figure out what it is.
That’s fair, if perhaps a bit pedantic. I suppose I was expecting some explanation of why the language of the new license would address these “whys” as opposed to just a list of grievances.
> hack the source code to grant yourself access to our paid features without a subscription, or the use of modified versions in production.
I think the change that you can’t modify the code and use it yourself in production is a big change that is glossed over. ES is now free as in beer. You can look at the code but you can’t touch it or change what it does.
Edit: I was wrong about this. The license itself does not say this, but the blog post seemed to indicate that it was a change. I think it’s an exclusive inclusive or problem.
This is false. License [0] clearly states the conditions under which you can do it and they seem pretty reasonable. Nothing that a normal user, faced with an issue they want to fix, wouldn't accept. I imagine Amazon would have trouble accepting those and other terms, but that's the whole idea.
No, you are both correct. You are talking about the SSPL, the parent poster you are replying to is talking about the Elastic License which does in fact prevent you from modifying the code and running it in production:
With the dual-licensing you have a choice of Elastic license or SSPL, but they both have terms you might not like. And if you use the binaries you automatically use the free as in beer Elastic license.
