🎉 Source Amazon S3: Fix docs link issue

[lazebnyi]

What

Fix link in docs

How

Fix name of section in docs

Pre-merge Checklist

Updating a connector

Community member or Airbyter

• Grant edit access to maintainers (instructions)
• Secrets in the connector's spec are annotated with airbyte_secret
• Unit & integration tests added and passing. Community members, please provide proof of success locally e.g: screenshot or copy-paste unit, integration, and acceptance test output. To run acceptance tests for a Python connector, follow instructions in the README. For java connectors run ./gradlew :airbyte-integrations:connectors:<name>:integrationTest.
• Code reviews completed
• Documentation updated
  • Connector's README.md
  • Connector's bootstrap.md. See description and examples
  • Changelog updated in docs/integrations/<source or destination>/<name>.md including changelog. See changelog example
• PR name follows PR naming conventions

Airbyter

If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.

• Create a non-forked branch based on this PR and test the below items on it
• Build is successful
• If new credentials are required for use in CI, add them to GSM. Instructions.
• /test connector=connectors/<name> command is passing
• New Connector version released on Dockerhub and connector version bumped by running the /publish command described here

[Phlair]

@lazebnyi Couple of Qs:

• Does this have the potential to break existing connections because of the name change? I'm genuinely not sure so hoping you've tested that.
• What's the motivation behind this change? This connector can actually be used for non-Amazon S3 compatible storage, so it seems incorrect to call it Amazon S3...

[lazebnyi]

@Phlair

1. Changes doesn't break existing connections. Tested locally.
2. Agree with you. For my side I think S3 name for the connector is ok. So, @misteryeo could you approve that we can leave S3 and close issue?

[misteryeo]

Thanks for the clarification on this - wasn't aware.

The problem I was trying to tackle here is that we've come across users who type 'Amazon' expecting to surface 'S3'. I imagine that we'll start seeing folks type 'Minio' and not be able to find anything either. This would apply for both the source and destination.

So the ideal situation here seems to be that the display name stays as 'S3' but we have some way of allowing search terms to surface this connector and those search terms being 'Amazon' and 'Minio'. What would it take for us to introduce this? cc: @sherifnada

[sherifnada]

@misteryeo we need to add some notion of search terms to connectors. This is an OSS platform + Frontend change

[lazebnyi]

@Phlair Reverted name to S3. Plz review.

[Phlair]

👍