Optimizing ETL times for Facebook connections in Airbyte on AWS EC2 instances

abctl used helm client under the hood, and whatever you pass there it will be configured for you deployment, so you need to pass everything you want.

<@U05JENRCF7C> I want to take a moment and say thank you! I am going to work on all these things, and I am surely not done with questions etc. but wanted to get that out before I do anything else :slightly_smiling_face:

I think this option --insecure-cookies can be done on values.yaml level
https://docs.airbyte.com/deploying-airbyte/integrations/authentication#disabling-secure-cookies

<@U05JENRCF7C> other than the blank/default values - does this values.yml look like it would cover my needs or am I mising anything?

  enabled: false

global:
  storage:
    type: "S3"
    storageSecretName: airbyte-config-secrets
    bucket:
      log: airbyte-bucket
      state: airbyte-bucket
      workloadOutput: airbyte-bucket
    s3:
      region: "us-east-1"
      authenticationType: credentials
  auth:
    cookieSecureSetting: "false"
  database:
    secretName: ""
    host: ""
    port: ""
    database: ""
    user: ""
    passwordSecretKey: ""
  ingress:
    enabled: true
    hosts:
      - host: "airbyte.example.com"
        paths:
          - path: "/"
            pathType: ImplementationSpecific
    annotations: {
      nginx.ingress.kubernetes.io/proxy-body-size: "16m",
      nginx.ingress.kubernetes.io/proxy-send-timeout: "1800",
      nginx.ingress.kubernetes.io/proxy-read-timeout: "1800"
    }```