Error with AWS Access Key Id after upgrading helm charts on EKS

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

Summary

After upgrading to the latest helm charts on EKS, encountering an error related to AWS Access Key Id not existing in records while using a service account. Need assistance in understanding if there are specific config values in the helm charts that need to be adjusted.


Question

Hi, running on EKS (deployed with the helm charts), was working fine until I upgraded to the latest 0.64.18 helm charts (was on 0.54.3)
i see the following error:
The AWS Access Key Id you provided does not exist in our records
why is it looking for access key id while i’m using a service account? is there something in the helm charts config values i need to change?
unclear from the documentation
thanks


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

["eks", "helm-charts", "aws-access-key-id", "service-account", "config-values"]
2

downgrading to charts version 0.54.3 worked of course
i’d add that i’m using S3 and removed completely MINIO

here are the config values i used which work with version 0.54.3


    externalDatabase:
      user: postgres
      database: airbyte
      existingSecret: airbyte-postgres-creds
      existingSecretPasswordKey: db-password
      host: <http://clue-data-dev-airbyte.cmyyz04mg46z.eu-west-1.rds.amazonaws.com|clue-data-dev-airbyte.cmyyz04mg46z.eu-west-1.rds.amazonaws.com>

    global:
      serviceAccountName: airbyte

      storage:
        type: S3

      database:
        secretName: airbyte-postgres-creds
        secretValue: db-password

      log4jConfig: "log4j2-no-minio.xml"
      logs:
        minio:
          enabled: false
        storage:
          type: "S3"
        s3:
          enabled: true
          bucket: clue-data-dev-airbyte-logs
          bucketRegion: eu-west-1

      state:
        storage:
          type: "S3"

      jobs:
        resources:
          limits:
            cpu: 1
            memory: 4Gi
          requests:
            cpu: 0.5
            memory: 256Mi

    serviceAccount:
      create: true
      name: airbyte
      annotations:
        <http://eks.amazonaws.com/role-arn|eks.amazonaws.com/role-arn>: arn:aws:iam::814382091013:role/data-dev-AirbyteServiceAccount

    worker:
      hpa:
        enabled: true

      resources:
        limits:
          cpu: 1000m
          memory: 4Gi

        requests:
          cpu: 256m
          memory: 512Mi

      extraEnv:
        - name: STATE_STORAGE_S3_BUCKET_NAME
          value: "clue-data-dev-airbyte-logs"
        - name: STATE_STORAGE_S3_REGION
          value: "eu-west-1"
        - name: S3_MINIO_ENDPOINT
          value: ""

    postgresql:
      enabled: false```
3

when trying to upgrade i added

        type: S3```
and then i got the `AWS Access Key Id` issue as mentioned