Before you deploy to the Production environment, download the Launch checklist, and use it with these instructions to confirm that you have completed all required configuration and testing. See an overview of the complete deployment process for Starter and Pro at Deploy your store.
See Test deployment for testing all aspects of your sites, stores, and environments. These tests include verifying Fastly, User Acceptance Tests (UAT), and performance testing.
Adobe provides a Let’s Encrypt SSL/TLS certificate for each environment. This certificate is required for Fastly to serve secure traffic over HTTPS.
To use this certificate, you must update your DNS configuration so that Adobe can complete domain validation and apply the certificate to your environment. Each environment has a unique certificate that covers the domains for the Adobe Commerce on cloud infrastructure sites deployed in that environment. We recommend completing and the configuration updates during the Fastly set up process.
When you are ready to launch your site, you must update the DNS configuration to route traffic from your Production environment through the Fastly service.
Production environment configuration has been updated with all required domains
Typically, you work with your Customer Technical Advisor to add all top-level domains and subdomains required for your stores. To add or change the domains for your Production environment, Submit an Adobe Commerce Support ticket. Wait for confirmation that your project configuration has been updated.
On Starter projects, you must add the domains to your project. See Manage domains.
SSL/TLS certificate provisioned for your production environments.
If you added the ACME challenge records for your Production domains during the Fastly setup process, Adobe uploads the SSL/TLS certificate to your Production environment automatically when you update the DNS configuration to route traffic to the Fastly service. If you did not pre-provision the certificate, or if you updated your domains, Adobe must complete domain validation and provision the certificate, which can take up to 12 hours.
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.
Add CNAME records to point the subdomains for your Production environment to the Fastly service
prod.magentocloud.map.fastly.net, for example:
|Domain or Subdomain||CNAME|
If needed, add A records to map the apex domain (
<domain-name>.com) to the following Fastly IP addresses:
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).
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.
Wait a few minutes for the site to update.
Test your site.
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:
Test and verify that Fastly caching is working correctly on the Production site. For detailed tests and checks, see Fastly 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 so on.
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.