Trouble setting up Airbyte on AWS EKS with external RDS database using Helm chart

  postgresql:
  	enabled: false
  database:
    type: "external"
    secretName: "airbyte-config-secrets"
    host: "${DATABASE_HOST}"
    port: "${DATABASE_PORT}"
    database: "${DATABASE_NAME}"
    userSecretKey: "DATABASE_USER"
    passwordSecretKey: "DATABASE_PASSWORD" ```

this it how it should be write ?

configuration that I shared is a template in terraform code host, port, database are replaced with real values, and secret airbyte-config-secrets is set separately
if you have something similar it shouldn’t be a problem

an issue here is with temporal component that it cannot work properly with enforced ssl

you can check this workaround I found or set rds.force_ssl to 0 if your RDS is in private subnet and security group for database allows only traffic from your Airbyte deployment

<@U07MQQ1J611> yup working no issues on 13.x

Airbyte Authentication/Login Issue

Guys need some help/input on authentication part for Airbyte this is how my helm values file look like

  # -- Auth configuration
  auth:
    # -- Whether auth is enabled
    enabled: true
    # -- Admin user configuration
    instanceAdmin:
      # -- Secret name where the instanceAdmin configuration is stored
      secretName: "airbyte-config-secrets"
      # -- The first name of the initial user
      firstName: "Admin"
      # -- The last name of the initial user
      lastName:  "Admin"
      # -- The key within `emailSecretName` where the initial user's email is stored
      emailSecretKey: "instance-admin-email"
      # -- The key within `passwordSecretName` where the initial user's password is stored
      passwordSecretKey: "instance-admin-password"           ```
So with this on first time I am getting setting page once its configured next time on login it doesnt allow the initial user to login as well. I even tried to login with email and password stored in secrets that also fails. It will be very nice to know you guys have done it

Just to be sure, abctl or helm charts?

it might be this case https://docs.airbyte.com/deploying-airbyte/integrations/authentication#disabling-secure-cookies

I am using helm chart and its deployed in AWS EKS

have you tried https://docs.airbyte.com/deploying-airbyte/integrations/authentication#disabling-secure-cookies ?
do you have host over http or https?