Custom domain setup

purple provides easy and convenient support for custom domains on your web experience website this article guides you through the set up of a custom domain for your purple web experience if you encounter any issues, please contact purple support for assistance preconditions an available sub domain unless your dns provider supports alias/aname records, you cannot use the root (apex) domain but instead need to use a sub domain example example org is the root domain www example org is a subdomain of example org if you use a sub domain, you will need to take care of forwarding the http requests from the root domain to the sub domain yourself we do not provide this functionality access to the dns server configuration of that domain a purple app with configured web experience the domain must not use cloudfront if the domain is already set up with a cloudfront instance, it first must be removed from the other cloudfront to set up cloudfront with purple how to guide 1\ go to purple manager – 'apps' – 'overview' 2\ click on the three dots menu 3\ click on 'experience' in the dropdown 4\ next to 'web newsstand domain' enter your desired domain name for the web experience for example, epaper example com 5\ click on 'update' 6\ click on 'ok' 7\ wait until the page shows dns records for the certificate 8\ configure the dns records in your dns server configuration create the cname record with the data shown in the ui aws needs this entry to be able to create a ssl certificate for the domain to use with the cloudfront cdn it may take a few minutes for aws to check and create the certificate after you created the dns entry do not remove this record after successful configuration it is needed for continued ssl support (renewal of certificates) 9\ wait until the page in purple manager shows the domain name for the cloudfront domain 10\ configure the custom domain to point to the cloudfront domain using a cname in the dns server configuration this step can be done at a later time, e g when the website should be made available to prepare for a switch over, all previous steps should be done at least 24 hours before the planned switch the existing dns entries should also be switched to a lower ttl value in advance so that the cut over time is as short as possible 11\ after a few minutes, the experience should be accessible via that domain name you have successfully configured the domain for your web experience, and the site is now publicly accessible