Configuring NGINX as a gateway

You can use the NGINX gateway configuration to avoid directly connecting to CloudBees Software Delivery Management API endpoint from your server. To do this, you need to configure NGINX as a gateway for forwarding connections between your private network servers and CloudBees Engineering Efficiency.

If you need to lock outbound access to the remote API endpoint to a fixed IP address, you can use: 34.68.172.197.

When using the proxy configuration for an integration, use the address of the NGINX server instead of https://app.cloudbees.com, as typically documented in the integration configuration procedures.

Configuring a basic setup

First, install NGINX and then update its configuration.

To configure a basic NGINX setup:

  1. Edit /etc/nginx/nginx.conf and add the following.

    events {
    }
    
    http {
      server {
        listen      80;
        location / {
          proxy_pass https://app.cloudbees.com;
        }
      }
    }

Configuring NGINX using HTTPS

To configure NGINX using HTTPS:

  1. Import your SSL certificate to /etc/ssl/certs/server.crt and your key to /etc/ssl/certs/server.key.

  2. Add the following content to /etc/nginx/nginx.conf.

Replace \{{domain_name}} with your preferred domain name. It should be valid for the provided certificates.

events {
}

http {
  server {
    listen      80;
    ## *******HTTPS specific setup**********
    listen      443 ssl http2;
    server_name \{\{domain_name}};

    ssl_certificate        /etc/ssl/certs/server.crt;
    ssl_certificate_key    /etc/ssl/certs/server.key;

    ssl_verify_client      off;
    ## ***********************************************

    location / {
      proxy_pass https://app.cloudbees.com;
    }
  }
}

After configuring NGINX, and restarting the server, all HTTP traffic sent to the NGINX endpoint should now be routed to https://app.cloudbees.com.