Summary
User is experiencing a configuration check failure when setting up the S3 source in Airbyte using an IAM role for authentication, despite successful role assumption via AWS CLI.
Question
Heya, I’m trying to set up self-hosted AirByte’s S3 source to work with the <S3 Connector | Airbyte Documentation“IAM Role” setup> (the help looks slightly different in the AirByte UI than in the docs site).
I have the policy + role + trust relationship (Edit: ~including external ID~) + user and all that set up. I can use the AWS CLI to confirm that the user can assume the role and read data from the given S3 bucket.
Then trying to set things up in the AirByte connector it fails with a configuration check. Did anyone else made it work with the role assumption?
If I directly attach the role to the user, it all works, of course. I just wanted to check whether this is expected to work?
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.