Installing Airbyte on EC2 instance without FQDN using abctl

Slack Knowledge Base Q&A Platform Questions
, , , ,
1

Summary

Clarification on installing Airbyte on an EC2 instance without FQDN using abctl and troubleshooting errors during installation. Query about native installation without Docker on a dedicated server.


Question

Hi Airbyte team, just wanted to clarify my understanding with you guys. I am trying install airbyte using abctl on my ec2 instance that does not have a FQDN:

  1. the host parameter expects FQDN so that airbyte can be accessed from outside. Previously I have tried installing using ip but it said that it doesn’t allow ip addresses as host. So for me to install airbyte and access it from outside I will need a FQDN. Is this correct? This is my understanding from the doc (https://docs.airbyte.com/using-airbyte/getting-started/oss-quickstart#using-an-ec2-instance-with-abctl)
  2. I get this error when I try installing:
    a. ERROR Cluster ‘airbyte-abctl’ could not be created
    b. ERROR unable to create kind cluster: failed to generate kubeadm config content: failed to get kubernetes version from node: failed to get file: command “docker exec --privileged airbyte-abctl-control-plane cat /kind/version” failed with error: exit status 126
  3. Can I do a native installation of airbyte without docker - if I have a dedicated server just for airbyte?
    Would really be helpful if the above are answered

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

["installing-airbyte", "ec2-instance", "abctl", "FQDN", "error", "native-installation", "dedicated-server"]