Branding the employee experience
      Back to home
      1. Knowledge Base
      2. Getting Started
      3. Branding the employee experience

      Set DNS for custom employee portal with Amazon Route53

      How to configure DNS to enable custom domain usage with CultureAI Security Centre

      Setting up a custom URL for your users to access the CultureAI security centre can be achieved by creating a CNAME record that points a subdomain to securitycentre.culture.ai. This guide walks through the steps required to set this up. 

      1. Choose your sub-domain 

      Choose a the sub-domain you want your end-users to be able to access security centre at under your domain. In this example we will use the sub-domain 'securitycentre'. Your users will be able to access the security centre at:

      https://securitycentre.yourdomain.com 

      2. Log into Amazon Route 53

      Log into the Amazon AWS Route 53 account where you manage your domains DNS records:

      https://console.aws.amazon.com/route53/home

      3. Click on your domain to open the record set screen

      Upon clicking your domain, you'll be taken to the record set screen.

      4. Click 'Create Record Set'

      Click the blue 'Create Record Set' button at the top of the screen. The 'Create Record Set' pane will open.

      5. Enter your chosen sub-domain

      In the 'Name' input field, enter your chosen sub-domain

      6. Select 'CNAME' in the type drop-down

      In the type drop down, select 'CNAME - Canonical name':

      7. Set the 'Value' field to 'securitycentre.culture.ai'

      In the 'Value' field, enter securitycentre.culture.ai. The default TTL of 300 seconds is fine, but you may change it if you wish. Keep the routing policy set to 'Simple'.

      8. Click 'Create'

      Click the blue 'Create' button at the bottom of the screen.

      9. Browse to https://securitycentre.yourdomain.com

      You should now be able to browse to https://securitycentre.yourdomain.com and see your security centre. In some cases, however, it may take up to 12 hours for the DNS records to propagate in which case you may see a DNS error. Please retry periodically over a few hours. If after 12 hours you still see an error, or are unsure you've configured the DNS correctly, please contact us.

      If you see an SSL certificate error, the custom domain has been set up correctly but please contact your service delivery manager whom will set up a valid SSL certificate for you.