Keyless has been tested on
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 i) ingress access to the appropriate TCP port; and ii) file system access to private keys (if filesystem storage is being used).
Supported operating system
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 (i.e., one that receives security updates) as your key server will have access to your private keys.
DNS record created within zone
openssl rand 24 -hexto generate a long, random hostname such as
- Add this record via your DNS provider’s interface as an ‘A’ record pointing to the IP address of your Keyless SSL server
- Use this hostname as the server hostname during initialization of your Keyless SSL server
Uploading “Keyless” SSL Certificates
Before your key server(s) 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.
It is recommended that you upload certificates to Cloudflare with only SANs that you wish to use with Cloudflare Keyless SSL. All hostnames you wish to use with Keyless SSL must be “orange clouded” (proxied) on Cloudflare.
For each certificate you wish to use with Keyless SSL:
Navigate to the Crypto app.
The final step in deploying Cloudflare’s Keyless SSL technology is installing the key server on your infrastructure, populating it with the SSL keys of the certificates you wish to use to terminate TLS at Cloudflare’s edge, and activating the key server so it can be mutually authenticated.
- Add the Cloudflare Package Repository as per .
- Amazon Linux customers need to manually set the yum
- 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
- Update your OS’ package listings, e.g.,
- Install the gokeyless server (min version used should be 1.5.3):
sudo apt-get install gokeyless
sudo yum install gokeyless
- Amazon Linux:
sudo yum install rsyslog shadow-utils && sudo yum install gokeyless
Add your Cloudflare account details to the configuration file located at
- Set the hostname of the key server, e.g.
- Set the Zone ID (can be found on the Cloudflare dashboard’s ‘Overview’ tab)
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
$ ls -l /etc/keyless/keys-r-------- 1 keyless keyless 1675 Nov 18 16:44 example.com.key
Note: when running multiple key servers, you must make sure that all required keys are distributed to each key server. Customers typically will either use a configuration management tool such as Salt, Puppet, etc. to distribute keys or mount
/etc/keyless/keysto a network location that is accessible only by your key servers. Keys are read on boot into memory, so if using a network path it must be accessible during the gokeyless process start/restart.
Restart your keyless instance:
sudo service gokeyless restart
sudo /etc/init.d/gokeyless restart
Network access control
During TLS handshakes, Cloudflare’s keyless client will initiate connections to the key server hostname or IP address you specify during certificate upload. By default, the keyless client will use a destination TCP port of 2407, but this can be changed during certificate upload or by editing the certificate details after upload.
Create firewall rules that allow your key server to accept connections from only Cloudflare. We publish our IPv4 and IPv6 addresses via our API.