I'm sorry, but as of the current information available, custom connectors are exclusive to Airbyte Open-Source deployments and are not yet supported on Airbyte Cloud. However, there are plans for their release on Airbyte Cloud, scheduled for January 2024. You can track the progress on this development [here](
https://github.com/orgs/airbytehq/projects/37?pane=issue&itemId=45471174). For using a custom connector with a Docker image in an open-source deployment of Airbyte, you would need to follow these steps: 1. Host your custom connector's Docker image on a private Docker registry. Here are some resources to create a private Docker registry, in case your organization does not already have one: [Google Cloud](
https://cloud.google.com/artifact-registry/docs/docker/quickstart), [AWS](
https://docs.aws.amazon.com/AmazonECR/latest/userguide/getting-started-console.html), [Azure](
https://docs.microsoft.com/en-us/azure/container-registry/container-registry-get-started-portal#:~:text=Azure%20Container%20Registry%20is%20a,container%20images%20and%20related%20artifacts.&text=Then,%20use%20Docker%20commands%20to,the%20image%20from%20your%20registry.), [DockerHub](
https://docs.docker.com/docker-hub/), [Self hosted](
https://docs.docker.com/registry/deploying/). 2. Authenticate your Airbyte instance to your private Docker registry. For example, if you're using Azure, you can authenticate to an Azure Container Registry using the
az
CLI:
az acr login --name <registry-name>
. You will have to authenticate both your local/CI environment/ environment (where your image is built) and your Azure Virtual Machine instance where the Airbyte instance is running. 3. Pull your connector image from your private registry to validate the previous steps. On your Airbyte instance: run
docker pull <image-name>:<tag>
if you are using our
docker-compose
deployment, or start a pod that is using the connector image. 4. In the Airbyte UI, go to the Admin section, and click on
[+ New connector]
on the top right. Fill in the required details like the display name, the Docker repository name (repository + image name), tag and documentation URL for that connector. 5. Once this is filled, you will see your connector in the UI and your team will be able to use it, from the UI and Airbyte's API too. Please refer to the [official documentation](
https://docs.airbyte.com/operator-guides/using-custom-connectors) for more detailed steps and information.