To update DNS configuration for site launch:

  1. Update the following DNS configuration for your Production site:

    • Set all necessary redirects, especially if you are migrating from an existing site

    • Set the zone’s root resource record to address the hostname

    • Lower the value for the Time-to-Live (TTL) to refresh DNS information to point customers to the correct Production store

      We recommend a significantly lower TTL value when switching the DNS record. This value tells the DNS how long to cache the DNS record. When shortened, it refreshes the DNS faster. For example, you can change the TTL value from three days to 10 minutes when you are updating your site. Be advised that shortening the TTL value adds load to the DNS infrastructure. Restore the previous, higher value after site launch.

  2. Add CNAME records to point the subdomains for your Production environment to the Fastly service prod.magentocloud.map.fastly.net, for example:

    Domain or SubdomainCNAME
    www.<domain-name>.comprod.magentocloud.map.fastly.net
    mystore.<domain-name>.comprod.magentocloud.map.fastly.net
  3. If needed, add A records to map the apex domain (<domain-name>.com) to the following Fastly IP addresses:

    Apex domainANAME
    <domain-name>.com151.101.1.124
    <domain-name>.com151.101.65.124
    <domain-name>.com151.101.129.124
    <domain-name>.com151.101.193.124
IMPORTANT
The DNS instructions in RFC1034 (section 2.4) state that:
A CNAME record is not allowed to coexist with any other data. In other words, if suzy.podunk.xx is an alias for sue.podunk.xx, you can’t also have an MX record for suzy.podunk.edu, or an A record, or even a TXT record.
For this reason, DNS records should be type CNAME for subdomains and type A for apex domains (root domains). Discarding this rule can result in disruptions to your mail service or DNS propagation because you lose the ability to add other records, such as MX or NS. Some DNS providers may circumvent this by using internal customizations, but following the standard ensures stability and flexibility (such as change of the DNS provider).
  1. Update the Base URL.

    • Use SSH to log in to the Production environment.

      magento-cloud ssh -e production
      
    • Use the CLI to change the base URL for your store.

      php bin/magento setup:store-config:set --base-url="https://www.<domain-name>.com/"
      

    NOTE: You can also update the Base URL from the Admin. See Store URLs in the Adobe Commerce Stores and Purchase Experience Guide.

  2. Wait a few minutes for the site to update.

  3. Test your site.

Verify Production configuration

Make a final pass to validate the Production configuration for one or more stores. You can update the configuration in the Production environment. If settings are read-only, you may need to open an SSH connection and use CLI commands to change the configuration, or make configuration changes in your local environment. After you complete the updates, you can deploy the changes to Staging and Production environments.

The following are recommended changes and checks:

Verify Fastly caching

Performance testing

We recommend that you review the Performance Toolkit options as part of your pre-launch readiness process.

You can also test using the following third-party options:

  • Siege: Traffic shaping and testing software to push your store to the limit. Hit your site with a configurable number of simulated clients. Siege supports basic authentication, cookies, HTTP, HTTPS, and FTP protocols.

  • Jmeter: Excellent load testing to help gauge performance for spiked traffic, like for flash sales. Create custom tests to run against your site.

  • New Relic (provided): Helps locate processes and areas of the site causing slow performance with tracked time spent per action like transmitting data, queries, Redis, and more.

  • WebPageTest and Pingdom: Real-time analysis of your site pages load time with different origin locations. Pingdom may cost a fee. WebPageTest is a free tool.

Security configuration

Performance monitoring

You can use New Relic services for performance monitoring on Pro and Starter environments. On Pro plan accounts, we provide the Managed alerts for Adobe Commerce alert policy to monitor application and infrastructure performance using New Relic APM and Infrastructure agents. For details on using these services, see Monitor performance with Managed Alerts.

Next step

Launch steps

Next pageLaunch steps

Commerce