Setup a custom domain (Optional)

By default, Sandbox Studio is deployed behind an AWS CloudFront distribution. Users can access it using the CloudFront distribution URL that is output from the SandboxStudio-API stack.

However, in most organisations you will want to provide a more user-friendly, branded domain name (e.g. sandbox.example.com). This requires setting up a custom domain in CloudFront and updating your DNS provider to route traffic to Sandbox Studio.


1. Retrieve CloudFront distribution details


2. Choose your custom domain

Decide on the domain name that will be used for Sandbox Studio. Examples:

Make sure this domain is one you control in your DNS provider (such as Route 53, Cloudflare, or another registrar).


3. Update CloudFront distribution with Alternate Domain Name (CNAME)

CloudFront requires an SSL/TLS certificate for custom domains.


4. Provision an SSL/TLS certificate in ACM


5. Update your DNS provider

It may take up to 30 minutes (or more depending on TTL settings) for DNS changes to propagate.


6. Update the ACS URL in Identity Center

Since the login flow depends on the correct Assertion Consumer Service (ACS) URL, you must update the Identity Center SAML application configuration:

Example:
https://sandbox.example.com/api/auth/login/callback

This ensures SAML assertions are posted to the correct URL.

7. Update the Web App URL in Sandbox Studio

In your Sandbox Studio environment:

Example:
https://sandbox.example.com
  • You should now be able to access (and login) to your Sandbox Studio using the new domain.

 


Why This Matters


Revision #4
Created 2025-08-28 07:45:54 UTC by Andy
Updated 2025-09-09 20:44:14 UTC by Paul