Appian Cloud customers can request to customize site URLs to provide a personalized experience to end users. Upon creation, Appian Cloud sites are assigned a subdomain under the appiancloud.com domain. This guide outlines the steps required to change the Fully Qualified Domain Name (FQDN) of Appian Cloud sites to a custom domain.
Let’s follow the setup with an example. Let’s say your domain is “mycorp.org” and you have a site, namely, “production-acme” currently using appiancloud domain as “production-acme.appiancloud.com”. You want to customize this sites to use “mycorp.org” so that the end users can access the site using URL using “production-acme.mycorp.org”.
Here are some facts about customizing domains:
Currently, your Appian Cloud site uses 3 FQDNs:
Only the first FQDN is visible to end users. You can decide to customize:
Let’s come back to our example now:
Why do I need to setup 3 domains?
These new FQDNs are used for background web requests to support features such as Document Component Viewer, Custom SAIL extensions, etc. and are needed for security purposes. Please review the Appian product documentation on these features for more details.
Now that you understand the use case, here are the steps.
Note: When generating the CA-signed certificate required to set up a custom domain, Appian does not allow the use of SAN or wildcard certificates.
Steps to take when an existing certificate is close to expiration:
When the certificate is close to expiration, submit a new support case to notify Appian. Appian will generate a Certificate Signing Request (CSR) which can be used to have a new certificate issued from a Certificate Authority (CA). Do NOT generate a separate key. Provide Appian the new certificate in PEM format. On receiving the renewed certificate, Appian will update the certificates for the respective sites. This action does not require any downtime/maintenance window.
This article applies to all versions of Appian Cloud.
Last Reviewed: August 2020
© 2020 Appian. All rights reserved.