If you've verified that your AWS Access Key ID and Secret Access Key are correct, the issue might be with how these credentials are being passed to the Airbyte deployment on EKS via Helm. Here's a sample configuration from the extracts provided:

yaml logs:   accessKey:     password: "your_access_key"     existingSecret: ""     existingSecretKey: "AWS_ACCESS_KEY_ID"   secretKey:     password: "your_secret_key"     existingSecret: ""     existingSecretKey: "AWS_SECRET_ACCESS_KEY"   storage:     type: "S3"

Ensure that you've replaced

"your_access_key"

and

"your_secret_key"

with your actual AWS Access Key ID and Secret Access Key, respectively. If you're still encountering issues, it might be helpful to check the following: - Ensure that your S3 bucket is in the same region as specified in your configuration. - Verify that the IAM user associated with the provided Access Key ID has the necessary permissions to access the S3 bucket. The user will require [read and write permissions](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_examples_s3_rw-bucket.html) to objects in the bucket. If the issue persists, consider reaching out to the [Airbyte community on Slack](https://airbytehq.slack.com) for further assistance.