Issue connecting to Airbyte on AWS Ubuntu EC2 instance

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

Summary

User is facing issues connecting to Airbyte installed on an AWS Ubuntu EC2 instance. They have followed the deployment steps and are stuck at accessing Airbyte via localhost. They suspect the issue might be related to the ‘dataline-key-airbyte.pem’ file.


Question

Hi all,
I am having an issue with connecting to Aitbyte installed successfully on an AWS Ubuntu EC2 instance.
I was wondering whether you could help.

  1. I have followed the steps in https://docs.airbyte.com/deploying-airbyte/on-aws-ec2 on Ubuntu => all the services are created and are started as expected.
  2. I am on the last step:
SSH_KEY=~/Downloads/dataline-key-airbyte.pem
ssh -i $SSH_KEY -L 8000:localhost:8000 -N -f unbuntu@ec2-$INSTANCE_IP.compute-1.amazonaws.com```
I visit `<http://localhost:8000>` in my web browser.

4. When I launch `<http://localhost:8000>`  nothing is happening. The web browser is empty.

Would you know what is going on? Could the issue comes from the 'dataline-key-airbyte.pem' file. I am using a private key generated by AWS (as standard). Is that correct?

<br>

---

This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. [Click here](https://airbytehq.slack.com/archives/C021JANJ6TY/p1715608859736169) if you want to access the original thread.

[Join the conversation on Slack](https://slack.airbyte.com)

<sub>
["airbyte", "aws-ubuntu-ec2", "connection-issue", "dataline-key-airbyte.pem"]
</sub>
2

You can use any key. Are you running this outside the server, correct?
In the server, can you run docker ps to check if all services are runing properly?

3

I’m running outside the server indeed. Let me have a look at docker ps.

4

This very weird… docker ps indicates that Docker is not installed when the GitHub workflow indicates that this is the case… OK I’ll review each step one by one as there is something funny going on here. Thank you for your support

5

Actually I have managed to resolved my issue:

  1. I have made sure I used the Amazon Linux 2 AMI instead of of a Ubuntu image as I did originally, as this is mentioned in the documentation.
  2. Plus I made sure docker was started… Which it did not originally. I had to introduce an extra line " sudo chmod 666 /var/run/docker.sock". The docker install and start script that is working for me is pasted below.
    sudo yum update -y
    sudo yum install -y docker
    docker --version
    sudo chmod 666 /var/run/docker.sock
    docker ps
    sudo service docker start
    sudo usermod -a -G docker $(whoami)
    docker info