Hello Everyone! new to Airbyte. While attempting to configure s3 access (as source and via redshift) it works fine with Access key and Secret but when attempted to configure s3 as destination, the connection is failing (with same access and secret which is really strange). Documentation looks straight forward and I’m not sure what is missing here..

What's the error? Can you double check if the IAM role has S3 write access for that bucket?

Hi @Anand, as @Jags (Kloud.io) suggested, I'd suggest you double-check the S3 permission your role has on the targeted bucket. Reading and writing do not require the same permission set, which could explain why you can read your source but cannot write to the destination.

this has been resolved.. thank you for your suggestions.