Manmohan Tyagi
07/26/2023, 5:06 PMkapa.ai
07/26/2023, 5:07 PMnginx 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: 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)Manmohan Tyagi
07/26/2023, 5:18 PM