Requesting a custom domain name for applications hosted in Pega Cloud
For your applications that are hosted in Pega Cloud, you can use a custom domain name that conforms to your enterprise standards. By using a custom domain name, users of your Pega Cloud-hosted applications see domain names that are familiar to them. For example, if you already registered your domain (for example, www.CustomerSite.com), you can now host your Pega applications on CreditCard.CustomerSite.com instead of CreditCard.pegacloud.io.
The certificates that are generated by this process are protected and managed by Amazon Web Services (AWS). Pegasystems does not have direct access to view these secure artifacts. AWS provides Pegasystems a reference to the certificate, which Pega Cloud Operations uses to configure the endpoint for your cloud system.
You must have access to the administrator email for the domain.
To add your custom domain name to your Pega Cloud environment:
- Open a service request through My Support Portal, and provide the following information:
- Your custom domain name (for example, CustomerSite.com)
- The names of the environments for which you want the custom domain name to apply, for example, CreditCard-dev.pegacloud.io and CreditCard-prod.pegacloud.io.
- Your deadline for completing this request
- Approve the request from the AWS Certificate Manager to create a wildcard SSL/TLS certificate.
Pega Cloud Operations requests the generation of a wildcard certificate for the requested domain name from the AWS Certificate Manager. Before AWS generates the certificate, the owner of the specified domain must approve the request.
AWS sends the approval email to the administrator email for the domain. If the domain WHOIS registration is private, AWS tries various email addresses for the domain, such as admin@CustomerSite.com or info@CustomerSite.com.
- After you approve the request to create the SSL/TLS certificate, notify Pega Cloud Operations by updating the service request in My Support Portal. After the certificate is created, Cloud Operations associates the SSL/TLS certificate with your Pega Cloud deployments. You might experience a short interruption of service (less than one minute) while the update is processed.
- Create a CNAME record on the DNS server that owns the requested domain name. For example, your DNS administrator creates a CNAME that maps CreditCard.CustomerSite.com to CreditCard-prod.pegacloud.io, where CreditCard-prod.pegacloud.io is the original name of your provisioned system.
After your custom domain name is set up, you can still resolve the original DNS name of your system, such as CreditCard-prod.pegacloud.io. However, when you access the original DNS name, you receive an SSL certificate warning, because the referenced domain name does not match the deployed certificate.
Published October 6, 2016 — Updated March 9, 2017