Before you begin
Before uploading your TLS/SSL certificate, ensure that your private key is not password protected and your certificate information is PEM formatted. Any number of certificates can be uploaded, but no more than 48 unique certificates can be applied to a single Cloud WAF instance.
Viewing certificates and their details
To view a summary of all TLS certificates protecting your site with Cloud WAF:
- Log in to the Signal Sciences console.
- If you have more than one site, select the appropriate site.
- From the Corp Manage menu, select Cloud WAF Certificates. The Certificates page for your site’s Cloud WAF appears displaying a summary table that lists the name, domains, status, and expiration details for all certificates at your site.
To view more specific details about a particular TLS certificate, follow the steps above and then click the View button at the right of a specific site in the summary table.
Note: If TLS connections terminate at the Edge before requests are sent to Cloud WAF, then uploading a TLS certificate is optional. Always upload and use certificates if traffic is direct to the Cloud WAF using HTTPS.
To add a certificate, upload it by following the steps below:
- On the Certificates page, click Add certificate. A page where you can add certificate details appears.
- Fill out the certificate details as follows:
- In the Name field, enter a meaningful name that can help you manage the certificate and distinguish it from any others that may exist.
- In the Certificate body field, enter the body of the unencrypted, PEM-formatted server certificate provided by your certification authority. RSA 2048 and 4096 certificates can be used.
- In the Certificate chain field, enter the certificate chain, which is also known as the intermediate certificate. The certificate chain is not required for self-signed certificates.
- In the Private key field, enter your certificate’s private key.
- Click the Upload certificate button. The newly uploaded certificate appears on the Certificates page in the summary table.
After uploading your certificate, be sure to create a Cloud WAF instance to protect your origin. Keep in mind that, for requests coming from Fastly’s Edge, you can use a Fastly-managed TLS certificate instead when you create a Cloud WAF instance. In this case, uploading a TLS certificate is optional.
To proceed with uploading a certificate, we’ll need information about the certificate and details from the certificate itself.
- Name: This names the cert within our system and makes managing certificates easier. Ensure that your name is more than 4 characters.
- Private key
- Certificate body
- Certificate chain: Also known as the intermediate certificate. The certificate chain is not required for self-signed certificates.
Deleting a certificate
Certificates that aren’t in use can be deleted as long as your Cloud WAF is not actively being provisioned.
- On the Certificates page, click View to the far right of the certificate. The view certificate page appears.
- Click Remove certificate in the upper-right corner of the page.