Cloudflare Tunnel setup

Through an integration with Cloudflare Tunnel, you can send traffic to a key server through a secure channel and avoid exposing your key server to the public Internet.

​​ Before you begin

​​ Supported platforms

Keyless has been tested on amd64 and arm architectures. The key server binary will likely run on all architectures that Go supports. Code support may exist for other CPUs too, but these other architectures have not been tested.

In addition to running on bare metal, the key server should run without issue in a virtualized or containerized environment. Care will need to be taken to configure ingress access to the appropriate TCP port and file system access to private keys (if using filesystem storage).

​​ Supported operating systems

You will need to be running a supported operating system (OS) to run Keyless. Supported operating systems include:

• Ubuntu 12.04.5 LTS, 14.04 LTS, 15.10, 16.04, 17.10
• Debian 7, 8, 9
• RHEL and CentOS 6, 7
• Amazon Linux 1, 2

We strongly recommend that you use an operating system still supported by the vendor (still receiving security updates) as your key server will have access to your private keys.

​​ Step 1 - Install cloudflared on key server

First, install cloudflared on your key server.

This process differs depending on whether you are using the command line or the Cloudflare dashboard.

​​ Step 2 - Create a Tunnel

Then, create a Cloudflare Tunnel.

This process differs depending on whether you are using the command line or the Cloudflare dashboard.

In these steps, you should choose the option to Connect a network and use the private IP address of your key server.

After you create the Tunnel, use the Cloudflare API to List tunnel routes, saving the following values for a future step:

• "virtual_network_id"
• "network"

​​ Step 3 - Upload Keyless SSL Certificates

Before your key servers can be configured, you must next upload the corresponding SSL certificates to Cloudflare’s edge. During TLS termination, Cloudflare will present these certificates to connecting browsers and then (for non-resumed sessions) communicate with the specified key server to complete the handshake.

Upload certificates to Cloudflare with only SANs that you wish to use with Cloudflare Keyless SSL. All Keyless SSL hostnames must be proxied.

You will have to upload each certificate used with Keyless SSL.

To upload a Keyless certificate with the API, send a POST request that includes a "tunnel" object.

"tunnel": {
  "vnet_id": "<VIRTUAL_NETWORK_ID>",
  "private_ip": "<NETWORK>"
}

​​ Step 4 - Set up and activate key server

Finally, you need to install the key server on your infrastructure, populate it with the SSL keys of the certificates you wish to use to terminate TLS at Cloudflare’s edge, and activate the key server so it can be mutually authenticated.

​​ Install

1. Add the Cloudflare Package Repository as per https://pkg.cloudflare.com/ Open external link .
2. Amazon Linux customers need to manually set the yum $releasever value:
   • Amazon Linux 1: sudo sed -i 's/$releasever/6/' /etc/yum.repos.d/cloudflare.repo
   • Amazon Linux 2: sudo sed -i 's/$releasever/7/' /etc/yum.repos.d/cloudflare.repo
3. Update your OS’ package listings, e.g., apt-get update or yum makecache.
4. Install the gokeyless server (min version used should be 1.5.3):
   • Debian/Ubuntu: sudo apt-get install gokeyless
   • RHEL/CentOS: sudo yum install gokeyless
   • Amazon Linux: sudo yum install rsyslog shadow-utils && sudo yum install gokeyless

​​ Configure

Add your Cloudflare account details to the configuration file located at /etc/keyless/gokeyless.yaml:

1. Set the hostname of the key server, for example, keyserver.keyless.example.com. This is also the value you entered when you uploaded your keyless certificate and is the hostname of your key server that holds the key for this certificate.
2. Set the Zone ID (found on Overview tab of the Cloudflare dashboard).
3. Set the Origin CA API key.

​​ Populate keys

Install your private keys in /etc/keyless/keys/ and set the user and group to keyless with 400 permissions. Keys must be in PEM or DER format and have an extension of .key:

$ ls -l /etc/keyless/keys
-r-------- 1 keyless keyless 1675 Nov 18 16:44 example.com.key

When running multiple key servers, make sure all required keys are distributed to each key server. Customers typically will either use a configuration management tool such as Salt or Puppet to distribute keys or mount /etc/keyless/keys to a network location accessible only by your key servers. Keys are read on boot into memory, so a network path must be accessible during the gokeyless process start/restart.

​​ Activate

To activate, restart your keyless instance:

• systemd: sudo service gokeyless restart
• upstart/sysvinit: sudo /etc/init.d/gokeyless restart

If this command fails, try troubleshooting by checking the logs.