The way I understand it, AWS has been creating derivative products that don't work very well based on ELK. AWS has also not been contributing back to the community anything, while raking in the millions for https://aws.amazon.com/elasticsearch-service/the-elk-stack/
Many elastic pros recommend not using the AWS version because it doesn't operate properly.
While I am pro OSS I can understand why a company based on OSS would not want to subsidize a much larger AWS who is extracting value, and also, their direct competitor.
When I talked with AWS about an estimate for Managed ELK, and also, an EC2 based ELK, I received estimates > 50M a year. Crazy pricing
Disclosure: I work for AWS, but I do not work directly on Elasticsearch related services.
Elasticsearch is/was an "upstream" for Open Distro for Elasticsearch (which is a distribution / collection of software). As an "upstream", changes to the core Apache 2.0 licensed software was sent as pull requests to Elastic, which are usually merged. It isn't correct to say that AWS has not been contributing to the upstream Elasticsearch code under an Apache 2.0 license (and, also, signing the CLA to boot, which allows Elastic to relicense AWS contributions under SSPL).
Here's a sample of PRs from AWS developers that I could find:
Many elastic pros recommend not using the AWS version because it doesn't operate properly.
While I am pro OSS I can understand why a company based on OSS would not want to subsidize a much larger AWS who is extracting value, and also, their direct competitor.
When I talked with AWS about an estimate for Managed ELK, and also, an EC2 based ELK, I received estimates > 50M a year. Crazy pricing