S3 Destination Access Denied 403

Summary

Troubleshooting access denied 403 error when setting up S3 destination


Question

hey there!
I’m trying to set a S3 destination, but always return acess denied 403.
with the same acess key and secret key i’ve set my dremio fine, and other tools.
Someone knows about it??



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.

Join the conversation on Slack

["s3-destination", "access-denied-403", "connector"]

You might try to set Endpoint
<https://s3.sa-east-1.amazonaws.com>

i`ve tried, still denied…
the curious is that dremio works well with this key

https://github.com/airbytehq/airbyte/blob/386067d25aca9c867b1fe57702113223c23c2bbc/airbyte-cdk/java/airbyte-cdk/s3-destinations/src/main/kotlin/io/airbyte/cdk/integrations/destination/s3/BaseS3Destination.kt#L34-L44|https://github.com/airbytehq/airbyte/blob/386067d25aca9c867b1fe57702113223c23c2bbc[…]io/airbyte/cdk/integrations/destination/s3/BaseS3Destination.kt
another thing that comes to my mind are permissions themselves
are they restricted or with full access s3:* to whole bucket?

i got a API that return some key with null value, but when i run my connector builder doesnt return the null values, how to make to get the full response