• Is this your first time deploying Airbyte?: No • OS Version / Instance: Amazon Linux • Memory / Disk: 4Gb • Deployment: K8 • Airbyte Version: 0.40.11 • Source name/version: All • Destination name/version: Redshift with S3 Staging • Step: Worker Start up • Description: • This is the main message we have at the top of each sync log: • message=‘io.temporal.serviceclient.CheckedExceptionWrapper: java.util.concurrent.ExecutionException: java.lang.RuntimeException: io.airbyte.workers.exception.WorkerException: Running the launcher replication-orchestrator failed’, type=‘java.lang.RuntimeException’, nonRetryable=false The error above comes regardless of connector. Here’s a few cherry picked errors from the attached log as well • errors: $.access_key_id: object found, string expected, $.secret_access_key: object found, string expected • software.amazon.awssdk.services.s3.model.S3Exception: The request signature we calculated does not match the signature you provided. Check your key and signing method. (Service: S3, Status Code: 403, Request ID: 17233C9B8CA0B1E7) We are using the same S3 creds within the k8 deployment as we are within the connector. The credentials DO have blanket access to the bucket. We are able to generate objects in target bucket, and we do see all the logs getting generated into that bucket. Both source and destinations pass checks.