Troubleshooting custom connector building in Airbyte Open Source Edition on AWS EKS

Summary

Unable to build a custom connector due to SSL certificate verification error. Attempted to install root CA in the airbyte-connector-builder-server pod but facing issues with custom docker image creation and pod startup.


Question

Hi team,
We deployed Airbyte Open Source Edition with official Helm chart on AWS EKS cluster. Currently we are not able to build custom connector to connect to our internal service. Here is the logs from the pod:
HTTPSConnectionPool(host='<http://api.dev|api.dev>.<<http://our_domain_name.com|our_domain_name.com>>', port=443): Max retries exceeded with url: /v1/analytics/proposal (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1129)')))
As I understand the error, I need to install the root CA in the airbyte-connector-builder-server pod.
Below are the steps I took to try to fix the error.
I tried to create a custom docker image based on the official airbyte/connector-builder-server image, then copy my root CA file, install the ca-certificates OS package and run the update-ca-trust OS command. After helm upgrade with my custom image, my pod just won’t start with error 127 in kubernetes logs and an error in the logs of the pod itself - /bin/bash: airbyte-app/bin/airbyte-connector-builder-server: No such file or directory.
I’ll be appreciate to any help.
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

["airbyte-open-source-edition", "aws-eks", "custom-connector", "ssl-certificate", "root-ca", "docker-image", "pod-startup"]