Hello. I am currently trying to upgrade to the latest airbyte release. I have been using airbyte to sync from postgres to s3. Postgres source still works. But when I try to setup my bucket destination, it gives me 403 error, even though I know I am providing the correct creds. Airbyte logs mentions that the bucket does not exist, but it does. However, the bucket name has a digit in the beginning, in this case

7b-lakehouse-dev

. Is there a chance that in the latest s3 destination it does not like the

digit

as the first letter in the bucket name?….

@Marcos Marx (Airbyte) turned this message into a ticket to ensure timely resolution!

Hi, I'm looking into this now and I'll let you know when I have more information.

Yo Sunny, thanks for checking it.

Hey there, I don't think this is related to the name since you're getting a 403 and not a 404. I can't find any 403 with that message in the s3 error response list, do you have the exact log message? If it is definitely 403, then could you try reviewing the bucket policy and IAM to make sure the user is granted access?

@Sunny Hashmi (Airbyte) So I never claimed this is an actual issue, it was more a question. Hence why I said

chance

. I am currently using

account key and secret key

. And in version

0.39.32-alpha

it all works fine. I then replicated the same settings, but to the latest version, does not work. So I need to go over the deployment again then, I can’t find anything that is different from before but yeah.