Before you begin

Choose a hostname

This will be the fully qualified domain name (FQDN) used to access the server where Flow Enterprise is installed. This should be something that can be pointed to the server directly or to a load-balancer, if you choose to use one.

For example, if you choose, the system will be available to users at

For more information, see Amazon's documentation on registering a domain name in AWS Route53 (external site, opens in new tab).

Trial Tip: Flow Enterprise can be installed even if you have not set up a hostname, however, Flow Enterprise cannot be fully configured without a valid hostname (FQDN).

back to top

Purchase or Generate TLS/SSL Certificates

Flow Enterprise requires that you have TLS/SSL certificates to function.  This is for security purposes and is configured through the administration console.

It is recommended that you purchase certificates for this specific purpose. For example, if you chose for your hostname, you should purchase an TLS/SSL certificate for that hostname. However, you are also welcome to do self-signed certificates. This is especially useful if you are a large organization with your own certificate authority. It is also acceptable to utilize wildcard certificates. For example, a wildcard certificate for * would work fine for

For more information, check out Obtaining Certificates.

Regardless of how you obtain them, you will need to do some preparation on the certificates prior to uploading them to the server. Replicated's console, and Flow, both used a "combined" certificate format for handling intermediate certificates. To prepare, you will need the following:

  1. The private key, with no password, used to generate the certificate in PEM format
  2. The certificate itself in PEM format
  3. Any intermediate certificates, in PEM format.
  4. The root trusted authority certificate, if using an internally signed certificate, in PEM format.

Tip: Certificates should always be in base64 (plain text) format and never DER format.

Once you have gathered the certificates, you must assemble them into a file. This file is called a certificate bundle. Add the certificate contents to the file in this order:

  1. The certificate
  2. Any intermediate certificates
  3. The root trusted authority certificate

The resulting file (certificate bundle) will look something like this if you have intermediate certificates:

(Your Primary SSL certificate: server.crt)
(Your Intermediate certificate: DigiCertCA.crt)
(Your Root certificate: TrustedRoot.crt)

If you do not have intermediate certificates, you will simply need a certificate file that contains your certificate. That file will look like:

(Your Primary SSL certificate: server.crt)

back to top

Find your email server

Flow Enterprise requires an e-mail server so that it can send e-mails to your users. Before you do the installation, you should gather the following data:

  • The hostname, port, username, and password for an SMTP server that can send e-mail to your users.
  • Choose an e-mail address that you want system e-mails to come from and provision it with your main provider. For example, if you choose, users will see that e-mail address on all e-mails from the system.

This e-mail server and information is required for the system to function. You must choose an e-mail server that meets the following criteria:

  • It must be able to send e-mail from the e-mail you choose to use as the "From" address in system e-mails.
  • It must be able to send e-mail to any users you intend to invite into the system.
  • It must be able to be reached on the given hostname and port from your chosen server.
  • It must not be a one-off installation of SendMail or Postfix on the local host server running the application.

Trial Tip: Flow can be installed even if a connection to the SMTP server is not possible during the install.

back to top

If you need help, please contact Pluralsight Support.