Use the same DNS with a different sub-domain for the release portal. For example, if the product is available at
atlan.xyz.com, release portal can be
Subdomain mapping for the release portal should be on the same ELB address as the product. For example, if 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. Refer to the doc attached below for reference.
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 given at the bottom.
Deploy the new release created on the release portal after the configuration changes. Refer to this document for reference: How to deploy new releases.
You should now be able to access the Release portal UI over SSL. 🎉