Use the same DNS with a different sub-domain for the release portal. For example, if the product is available at
atlan.xyz.com, the release portal can be
The subdomain mapping for the release portal should be on the same ELB address as the product. For example, if the ELB for the product is
af9b5376955e644f2aab6b4aaaaa111b-1111111111.us-east-1.elb.amazonaws.com, then map the release portal to the same address.
SSL certificates should be uploaded on the release portal. For more information, check out the link below.
Details will be available in the output of the CloudFormation template.
For example, if the DNS record for the release portal UI is
abc-release.example.com as the domain name.
After updating the release portal domain, click on the "Save Config" button at the bottom.
After the configuration changes, you can deploy the new releases created on the release portal. For more information, visit this link: How to deploy new releases.
You should now be able to access the release portal UI over SSL! 🎉