I deployed the airbyte on AWS EC2 Linux - <https:/...
# replication-ask-ai
m
I deployed the airbyte on AWS EC2 Linux - https://docs.airbyte.com/deploying-airbyte/on-aws-ec2. I am able to access the airbyte - http://Ip:8000, working fine. I tried to proxy airbyte behind the nginx - here is the nginx config - --------------- server { listen 8090; listen [:]8090; server_name _; #root /usr/share/nginx/html; # Load configuration files for the default server block. #include /etc/nginx/default.d/*.conf; #error_page 404 /404.html; location = / { proxy_pass http://127.0.0.1:8000; proxy_read_timeout 900; # proxy_set_header Cookie $http_cookie; } ------------------------------------- Following - https://docs.airbyte.com/operator-guides/security Clear All Docker Images and docker compose down. .env change # Proxy Configuration # Set to empty values, e.g. "" to disable basic auth BASIC_AUTH_USERNAME="" BASIC_AUTH_PASSWORD="" Then docker compose up All containers running were successfully. Then try to access http://ip:8090 Page not loading. Just Showing airbyte logo. Then try- curl http://IP:8090/ output-- <!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <link rel="icon" href="/favicon.ico"> <meta name="viewport" content="width=device-width, initial-scale=1"> <meta name="theme-color" content="#000000"> <meta name="description" content="Airbyte is the turnkey open-source data integration platform that syncs data from applications, APIs and databases to warehouses." > <meta name="airbyte:sec-token" content="c82db11b-64df-413d-aba8-ee66b99c046f"> <meta name="airbyte:version" content="0.50.11"> <link rel="apple-touch-icon" href="/apple-touch-icon.png"> <link rel="manifest" href="/manifest.json"> <link rel="stylesheet" href="/index.css"> <title>Airbyte</title> <script type="module" crossorigin src="/assets/index-1019d442.js"></script> <link rel="stylesheet" href="/assets/index-61525523.css"> <script data-script="config-overwrites"> window.TRACKING_STRATEGY = "segment"; </script></head> <body> <noscript> <img src="/logo.png" alt="" width="90" height="94"> <div class="card">You need to enable JavaScript to run this app.</div> </noscript> <div id="root"></div> </body> </html> I also enabled the JavaScript On Browser, But No luck.
k
Sure, here is an example of an Nginx reverse proxy configuration that you can use for Airbyte:
Copy code
nginx server {    listen 443 ssl;    server_name airbyte.<your-domain>.com;    client_max_body_size 200M; # required for Airbyte API    ssl_certificate <path-to-your-cert>.crt.pem;     ssl_certificate_key <path-to-your-key>.key.pem;        location / {    proxy_pass <http://127.0.0.1:8000;>    proxy_set_header Cookie $http_cookie; # if you use Airbytes basic auth    proxy_read_timeout 3600; # set a number in seconds suitable for you    }   }
This configuration will listen on port 443 (the standard HTTPS port) and proxy all requests to your Airbyte instance running on
<http://127.0.0.1:8000>
. You will need to replace
<your-domain>.com
,
<path-to-your-cert>.crt.pem
, and
<path-to-your-key>.key.pem
with your actual domain name and the paths to your SSL certificate and key files, respectively. You can also change the default username and password in your environment's
.env
file:
Copy code
bash  # Proxy Configuration    # Set to empty values, e.g. "" to disable basic auth    BASIC_AUTH_USERNAME=your_new_username_here    BASIC_AUTH_PASSWORD=your_new_password_here
Please note that Airbyte currently does not include any user management or role-based access controls (RBAC) to prevent unauthorized access to the API or UI. Controlling who has access to the hardware and network your Airbyte deployment runs on is your responsibility. Source: [Airbyte Security](https://docs.airbyte.com/operator-guides/security)
m
I am trying very simple just nginx http-> airbyte http. server { listen 8090; listen [:]8090; server_name _; #root /usr/share/nginx/html; # Load configuration files for the default server block. #include /etc/nginx/default.d/*.conf; #error_page 404 /404.html; location = / { proxy_pass http://127.0.0.1:8000; proxy_read_timeout 900; # proxy_set_header Cookie $http_cookie; }