<@U04S8PLJWMT> i.a.w.s.a.OutputStorageClient(pers...
# ask-ai
r
@kapa.ai i.a.w.s.a.OutputStorageClient(persist):61 - Message: The authorization header is malformed; the region 'us-east-1' is wrong; expecting 'eu-west-1' (Service: S3, Status Code: 400, Request ID: TW1RSEY6MBVYF8ND, Extended Request ID: bynVIKxfhDJJ8CYQUJcYyw4RNw9zaZUAXXY111q7xg8cVKWnQgSTEMXzVNi5bnx5bqVr65JEO4Q=) (SDK Attempt Count: 1)
k
This error means Airbyte is trying to write to S3 using region
us-east-1
, but the target bucket actually lives in
eu-west-1
, so AWS rejects the request as having a malformed authorization header. You need to make the S3 region configuration in Airbyte match the real bucket region. Depending on what you’re configuring: ### 1. Platform state/logging storage (Helm / Kubernetes) In your
values.yaml
, set the correct region under
global.storage.s3.region
to
eu-west-1
, and redeploy:
Copy code
yaml global:   storage:     type: "S3"     secretName: airbyte-config-secrets     bucket:       log: your-bucket       state: your-bucket       workloadOutput: your-bucket     s3:       region: "eu-west-1"           # must match bucket's region       authenticationType: "credentials"  # or "instanceProfile"       # accessKeyId / secretAccessKey if using credentials
[[State/logging storage](https://docs.airbyte.com/platform/deploying-airbyte/integrations/storage#values)] You must also ensure the IAM user/role has permissions on that specific bucket and region. [[AWS policies appendix](https://docs.airbyte.com/platform/enterprise-setup/implementation-guide#aws-policies-appendix)] ### 2. S3 destination connector When configuring the S3 destination in the UI/API, set S3 Bucket Region to
eu-west-1
(the region where the bucket was created). [[S3 destination](https://docs.airbyte.com/integrations/destinations/s3#prerequisites)] If you still see the error after correcting the region, the knowledge sources don’t provide further S3 SDK–level debugging steps; you may need to verify in AWS which region the bucket is in and confirm all Airbyte configs referencing that bucket use the same region.
r
@kapa.ai But I have define the proper region
k
A message from kapa.ai
Given that the error still says: > the region
us-east-1
is wrong; expecting
eu-west-1
there is some S3 configuration inside Airbyte that is still using
us-east-1
, even if you’ve set
eu-west-1
in one place. From the docs, there are two separate S3 region settings you may need to align: 1. Platform state/logging storage (Helm / deployment level) In
values.yaml
(Helm), the region is set under
global.storage.s3.region
and is used for: - logs (
bucket.log
) - state (
bucket.state
) - workload output (
bucket.workloadOutput
) [[State/logging values](https://docs.airbyte.com/platform/deploying-airbyte/integrations/storage#values)] Example (must match your bucket region exactly):
Copy code
yaml    global:      storage:        type: "S3"        secretName: airbyte-config-secrets        bucket:          log: your-bucket          state: your-bucket          workloadOutput: your-bucket        s3:          region: "eu-west-1"          authenticationType: credentials # or instanceProfile
If you’re using an older chart structure (like the forum example you shared earlier with
logs.minio.enabled
/
s3.enabled
), you may need to update to the
global.storage
format; otherwise the new region setting may be ignored. [[EKS/IRSA example](https://github.com/airbytehq/airbyte/issues/53652)] 2. S3 destination connector config (per-connection) In the destination UI, S3 Bucket Region is a separate field and must also be set to
eu-west-1
. [[S3 destination setup](https://docs.airbyte.com/integrations/destinations/s3#step-2-set-up-the-s3-destination-connector-in-airbyte)] Because the stack trace references
OutputStorageClient
, it’s likely related to state/logging/workloadOutput rather than the destination connector itself. In that case, double‑check: - The effective
values.yaml
being deployed (e.g.,
helm get values <release>
), to ensure
global.storage.s3.region
is actually
eu-west-1
in the running release. - That there is no older
logs.s3.bucketRegion
or similar stanza still present from a previous values schema that might be overriding/used by your chart version. The docs only cover the newer
global.storage
structure; if you’re mixing schemas, behavior is undefined in the docs. [[State/logging values](https://docs.airbyte.com/platform/deploying-airbyte/integrations/storage#values)] If after verifying the deployed values and the S3 destination’s S3 Bucket Region you still see
us-east-1
in the error, the knowledge sources don’t provide additional internal debugging steps; at that point, capturing your exact
values.yaml
and Airbyte version and opening an issue or forum post would be the next documented path.