✨ Source S3: Add region to config

[hawkaa]

Fixes #20860

What

Adds support for specifying region as a part of specifying the S3 source connector.

How

Adds a new config item and passes it to the S3 client.

Recommended reading order

🚨 User Impact 🚨

No breaking changes. The new field is optional

Updating a connector

Community member or Airbyter

• Grant edit access to maintainers (instructions)
• Unit & integration tests added

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.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
airbyte-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 2, 2024 6:06am

[CLAassistant]

All committers have signed the CLA.

[github-actions]

Before Merging a Connector Pull Request

Wow! What a great pull request you have here! 🎉

To merge this PR, ensure the following has been done/considered for each connector added or updated:

• PR name follows PR naming conventions
• Breaking changes are considered. If a Breaking Change is being introduced, ensure an Airbyte engineer has created a Breaking Change Plan.
• Connector version has been incremented in the Dockerfile and metadata.yaml according to our Semantic Versioning for Connectors guidelines
• You've updated the connector's metadata.yaml file any other relevant changes, including a breakingChanges entry for major version bumps. See metadata.yaml docs
• Secrets in the connector's spec are annotated with airbyte_secret
• All documentation files are up to date. (README.md, bootstrap.md, docs.md, etc...)
• Changelog updated in docs/integrations/<source or destination>/<name>.md with an entry for the new version. See changelog example
• Migration guide updated in docs/integrations/<source or destination>/<name>-migrations.md with an entry for the new version, if the version is a breaking change. See migration guide example
• If set, you've ensured the icon is present in the platform-internal repo. (Docs)

If the checklist is complete, but the CI check is failing,

1. Check for hidden checklists in your PR description

2. Toggle the github label checklist-action-run on/off to re-run the checklist CI.

[marcosmarxm]

Thanks for the contribution @hawkaa sorry the lack of update. Are you still interested in continuing the contribution?

[hawkaa]

Thanks for the contribution @hawkaa sorry the lack of update. Are you still interested in continuing the contribution?

Yeah, would love to! What's next? I assume that I need to rebase the changes at the very least?

[marcosmarxm]

Thanks for the contribution @hawkaa sorry the lack of update. Are you still interested in continuing the contribution?

Yeah, would love to! What's next? I assume that I need to rebase the changes at the very least?

Yes please.

[hawkaa]

Thanks for the contribution @hawkaa sorry the lack of update. Are you still interested in continuing the contribution?

Yeah, would love to! What's next? I assume that I need to rebase the changes at the very least?

Yes please.

Done!

[tolik0]

@hawkaa, Could you please update your branch to the latest version? It would be best if you also populated the AWS region for the IAM client.

[hawkaa]

@hawkaa, Could you please update your branch to the latest version? It would be best if you also populated the AWS region for the IAM client.

Done!

[tolik0]

@hawkaa The PR with your changes is merged. Thank you for your contribution!