@kapa.ai I'm running airbyte in EKS. My worker and server pods are throwing the error "Unable to load AWS credentials from any provider in the chain:". I'm trying to upgrade from helm chart version 0.54.15 to 0.293.4.

Based on the knowledge sources provided, it seems like your issue might be related to the AWS credentials not being correctly passed to the

airbyte-worker

and

airbyte-server

containers. Here are some steps you can take to troubleshoot and resolve this issue: 1. Create or Update Kubernetes Secrets: If you're using AWS access keys, ensure that you've created a Kubernetes secret to store these credentials. You can do this by applying a Kubernetes manifest, replacing the example AWS credentials with your actual credentials. Here's an example of how to do this:

yaml apiVersion: v1   kind: Secret   metadata:     name: airbyte-config-secrets   type: Opaque   stringData:     s3-access-key-id: AKIAIOSFODNN7EXAMPLE # Enter your AWS Access Key ID here     s3-secret-access-key: wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY # Enter your AWS Secret Access Key here

(Source: [Airbyte Documentation](https://docs.airbyte.com/deploying-airbyte/on-kubernetes-via-helm#migration-steps-1)) 2. Update Airbyte Configuration: In your

airbyte.yml

configuration file, add the necessary configuration for AWS S3 and ensure that the

authenticationType

is set to

credentials

. 3. Update Helm Chart Configuration: Ensure that the AWS credentials are correctly passed to the

airbyte-worker

and

airbyte-server

containers in your Helm chart configuration. Here's an example of how to do this:

yaml server:     extraEnv:       - name: AWS_ACCESS_KEY_ID         valueFrom:           secretKeyRef:             name: airbyte-logs-secrets             key: AWS_KEY       - name: AWS_SECRET_ACCESS_KEY         valueFrom:           secretKeyRef:             name: airbyte-logs-secrets             key: AWS_SECRET_KEY

(Source: [Airbyte Documentation](https://docs.airbyte.com/deploying-airbyte/on-kubernetes-via-helm#external-logs-with-s3)) 4. Remove Deprecated Configuration: If you're upgrading from an older version of the Helm chart, ensure that any deprecated storage and secrets manager environment variables related to S3 and AWS Secrets Manager are removed from your

values.yaml

or

airbyte-pro-values.yaml

files. (Source: [Airbyte Documentation](https://docs.airbyte.com/deploying-airbyte/on-kubernetes-via-helm#migration-steps-1)) If you're still facing issues after following these steps, it might be helpful to check the Airbyte [GitHub issues](https://github.com/airbytehq/airbyte/issues) or [forum](https://discuss.airbyte.io/) for similar problems and potential solutions.

Suggestion 1 and 3 doesn't match. I need to set those env variables in two different sections? And it should be on airbyte-config-secrets or airbyte-logs-secrets ?

A message from kapa.ai