✨Source amazon-sqs: Allow role based access

[keiththompson]

What

Amazon SQS: Allow role based access.
Currently this connector only supports using AWS Users via access and secret keys. Adding an optional session token allows this connector to run with the role of a machine user.

https://medium.com/datamindedbe/why-you-should-not-use-iam-users-d0368dd319d3

How

I added an optional session_token field to the spec and passed it through to the boto3 session.

Recommended reading order

1. airbyte-integrations/connectors/source-amazon-sqs/source_amazon_sqs/spec.json
2. airbyte-integrations/connectors/source-amazon-sqs/source_amazon_sqs/source.py
3. airbyte-integrations/connectors/source-amazon-sqs/integration_tests/invalid_config.json

🚨 User Impact 🚨

Because the session_token is optional, existing users will not be affected by the change.

[vercel]

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

1 Ignored Deployment

Name	Status	Preview	Comments	Updated (UTC)
airbyte-docs	⬜️ Ignored (Inspect)	Visit Preview		Jun 13, 2024 3:50pm

[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.