Rename OpenSearch to "Amazon OpenSearch "

[adriens]

❔ Context

Currently, Amaon products all begin with Amazon :

.. except OpenSearch.

👉 Consequence

It's not that easy to get all AWS products grouped together (like we do for Apache)

[marcwrobel]

LGTM. I also added the alternate URL /amazon-opensearch.

[adriens]

Much better 👍

[adriens]

https://dev.to/adriens/comment/23dmi

[captn3m0]

Unsure about this one, Amazon Opensearch is the AWS Service, which we don't track. Opensearch the database, which we track is the upstream project. Opensearch is maintained by AWS, but using 'Amazon Opensearch' as the title makes it more confusing, imo.

There isn't clarity about the exact patch numbers being used on the AWS service, but it is quite possibly they lag behind the OSS version, similar to the /eks scenario.

[adriens]

Hmmm, my primary goal was to be able to list all AWS maintained software, for example for query purpose.
Are you thinking about another trick @captn3m0 ❔

[marcwrobel]

You are right @captn3m0, https://opensearch.org/ does not mention Amazon at all (except for mentioning OpenSearch is an AWS trademark).

So the distinction between OpenSearch (the software) and Amazon OpenSearch (the service) is quite clear.

I will revert the commit.

[marcwrobel]

@adriens, @captn3m0 : if that make sense maybe Amazon OpenSearch (the service) could be considered as a new product, distinct from OpenSearch (the software).

[adriens]

While reading the gh repo Welcome! section, it drives me to :

OpenSearch is a community-driven, open source fork

then to https://aws.amazon.com/blogs/opensource/introducing-opensearch/

So how could we flag it as belonging to AWS ? 💭

[captn3m0]

We can add tags in Jekyll, so we can use a aws tag for all aws affiliated projects, with perhaps a aws-service tag for AWS services.

[marcwrobel]

See discussion on #2036.