Summary
User is having trouble connecting to the Airbyte UI on an EC2 instance despite following steps in a YouTube video. Port 8000 and 80 are allowed in inbound policies.
Question
Could someone help me out the self hosted airbyte with ec2?
I followed the new youtube video here: https://www.youtube.com/watch?v=1yBBkzJizKk
This video was good. I was able to complete all the steps see airbyte running with docker ps, updated the ingress rule to have the A record name I created for the public IP of my ec2. I cannot seem to connect to the UI on port 8000. port 8000 and 80 are allowed on inbound polices. Any help would be much appreciated!
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
["self-hosted-airbyte", "ec2", "docker", "port-8000", "ingress-rule"]
Are you able to reach the machine at all or does your browser just sit forever loading?
I get “This site can’t be reached” ERR_TUNNEL_CONNECTION_FAILED
if you have dig installed on your machien, can you run dig <YOUR_A_RECORD_NAME>
and verify it is pointing to your public ip address?
and can you verifiy you can hit: http://YOUR_PUBLIC_IP:8000 that should return a 404 but that is expected.
Also you no longer have to edit the ingress, you can use the --host flag and that will set the ingress for you (for future runs of abctl)
okay, when I dig my A record name it says
;; SERVER: 127.0.0.53#53(127.0.0.53)
So I am thinking its not point to my public IP
yeah that does not look correct
I wonder if you can use the ec2 private ip for the A name record
Kinda depends on what you want to do. You can use a “private” dns name if you are only planning on accessing Airbyte from inside your VPC (or you want to setup a bastion host). If you want to be able to access your Airbyte instance from the internet, you will need a “public” dns record with the public IP in the A record.