Error running sync on Airbyte Helm Chart v1.1.1

Slack Knowledge Base Q&A Platform Questions
, , , ,
1

Summary

The user is facing an error ‘DocStoreAccessException’ while running a sync on Airbyte Helm Chart v1.1.1. The error is related to AWS S3 authorization header being malformed with incorrect region.


Question

Hi guys, I am facing issues when running a sync on airbyte helm chart v1.1.1 (latest). I got the next error:

ERROR i.a.c.ConnectorWatcher(handleException):175 - Error performing operation: io.airbyte.workers.workload.exception.DocStoreAccessException
io.airbyte.workers.workload.exception.DocStoreAccessException: Unable to write output for decd338e-5647-4c0b-adf4-da0e75f5a750_4821_2_check
at io.airbyte.workers.workload.JobOutputDocStore.writeOutput(JobOutputDocStore.kt:72) ~[io.airbyte-airbyte-commons-worker-1.1.0.jar:?]
at io.airbyte.workers.workload.JobOutputDocStore.write(JobOutputDocStore.kt:38) ~[io.airbyte-airbyte-commons-worker-1.1.0.jar:?]
at io.airbyte.connectorSidecar.ConnectorWatcher.saveConnectorOutput(ConnectorWatcher.kt:163) [io.airbyte-airbyte-connector-sidecar-1.1.0.jar:?]
at io.airbyte.connectorSidecar.ConnectorWatcher.run(ConnectorWatcher.kt:72) [io.airbyte-airbyte-connector-sidecar-1.1.0.jar:?]
at io.airbyte.connectorSidecar.ApplicationKt.main(Application.kt:32) [io.airbyte-airbyte-connector-sidecar-1.1.0.jar:?]
at io.airbyte.connectorSidecar.ApplicationKt.main(Application.kt) [io.airbyte-airbyte-connector-sidecar-1.1.0.jar:?]
Caused by: software.amazon.awssdk.services.s3.model.S3Exception: The authorization header is malformed; the region 'us-east-1' is wrong; expecting 'eu-west-1' (Service: S3, Status Code: 400, Request ID: KKJSNCAD9MQEBX77, Extended Request ID: tX73oYE3fEFP+thT4mm0pXcFvsuay/w2L6FhsO5hWrEeeeIvaoJEjr78NnKE1a/sNt0/3CeEEag=)
at software.amazon.awssdk.protocols.xml.internal.unmarshall.AwsXmlPredicatedResponseHandler.handleErrorResponse(AwsXmlPredicatedResponseHandler.java:156) ~[aws-xml-protocol-2.27.8.jar:?]

But when describing the pod source-postgres-check-4821-2-lflrt I can see already set the envvars for aws access keys so due the error I am assuming it is not picking it up for some reason. Thanks in advance for any help.


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

["error", "sync", "airbyte", "helm-chart", "docstoreaccessexception", "aws-s3", "authorization-header", "malformed", "region"]