According to the release blogpost [0], "SQL Support [...]is an improved version of the elasticsearch-sql plugin."
Sounds like they are building on it, as you suggested.
[0] https://aws.amazon.com/blogs/aws/new-open-distro-for-elastic....
Looks like it was. https://github.com/opendistro-for-elasticsearch/security-ssl...
floragunn GmbH Copyright 2015-2018 floragunn GmbH
https://github.com/opendistro-for-elasticsearch/security/blo...
More generally: why should AWS get to leverage its near-monopolistic position in the SaaS market to perform essentially hostile takeovers of the software projects it packages and runs? Simply because they have the resources to do it?
The code was open, and the company decided to close it for the new versions, so it forks. Forks are common when people don't like the corporate direction of an OSS project - It's a strength, not a weakness. Openoffice/Libreoffice, Hudson/Jenkins etc.
Imagine if Linus said that the next version of Linux would be paid-only.
Within 15 minutes there'd be a new librelinux repo that people could contribute to instead.
Someone was going to make a new fork anyway - This is Amazon putting their money where their mouth is to fund and support that new fork.
Would you feel the same if AWS built a drop in/api compatible system from scratch?
Why wasn't ElastAlert used / built upon for alerting? https://github.com/yelp/elastalert
Or why wasn't ElasticSearch SQL used / built upon for SQL? https://github.com/NLPchina/elasticsearch-sql
Or why wasn't SearchGuard used / built upon for Security? https://github.com/floragunncom/search-guard
All of them have Apache 2.0 license.