Go Live Checklist
Use this checklist to verify that your Bloomreach Cloud environment is ready for production.
Checklist
- Submit SSL certificates to the Bloomreach Cloud team. Encrypt all secrets using the provided PGP key.
- Schedule reminders to renew certificates before they expire.
- Do not use
bloomreach.clouddomains in production for either headless or classic HST implementations. - Use separate (sub)domains for the CMS and the site web application or delivery API. For example, use
cms.customername.comfor the CMS andprod.customername.comfor the site.
- After the Bloomreach Cloud team installs the certificates, configure your domains to point to the correct environment.
- Set up virtual hosts for both the site and the CMS in the target environment.
- Verify domain and certificate configuration locally. Add the domains to your local hosts file and point them to the stack to confirm correct routing.
- If your website needs to send email, configure the SMTP server for your stack.
- Configure your CDN or use the Bloomreach Cloud-provided CDN as required. Do not use the
bloomreach.clouddomain for production. Contact support for guidance if needed. - Perform a performance test to confirm that your Bloomreach Experience Manager implementation supports the expected load.
- Monitor search queries from the website, as these may be resource-intensive or slow. Review external API calls for similar issues.
- Mark the environment as Production and use your public URL or an alias (such as
www2.company.com) for testing. - Enable HST caching.
- Confirm the following:
- Change all default passwords (for example, admin/admin) to secure values.
- The CMS and Channel Manager are accessible and functional via your public URLs.
- The site does not rely on HTTP session state except for caching purposes.
- The site behaves correctly with redirects when accessed through the public URL (for example, after user login).
- Notify the Bloomreach Cloud support team of your planned Go Live date at least one week in advance.
- Configure all required DNS records. For more information, see the FAQ.