If you have a live site up-and-running on your production domain (
example.com) and you need to test your new store on Adobe Commerce on cloud infrastructure’s Production environment with Fastly CDN enabled, we recommend using the subdomain (like
prod.example.com), having previously added it to Fastly, for any pre-launch testing activities. This article discusses the details and provides useful links to the related Adobe Commerce documentation resources.
Your current store that uses the
example.com production domain is live and operating. However, you need to test your new store, built with Adobe Commerce on cloud infrastructure and deployed to the Production environment, with the Fastly full page cache service enabled.
The problem is that the Production environment of your Adobe Commerce on cloud infrastructure project uses the same live domain (
example.com), and you cannot switch your new site to this domain, simultaneously having your current live store running – on the same domain.
In theory, you could skip using Fastly CDN and test your Adobe Commerce on cloud infrastructure store on the Production environment without full page cache enabled.
However, with full-page cache enabled, your store performs differently; you never know the real live performance of your site if you have not tested it with CDN before launching. Testing your store on Production with Fastly CDN enabled is the official Adobe Commerce recommendation.
Use the first-level subdomain (
prod.example.com) for your new Adobe Commerce on cloud infrastructure store on the Production environment while keeping the current live site on the base domain (
When planning your Adobe Commerce on cloud infrastructure project, you may specify such a production subdomain and request the cloud infrastructure team to point the subdomain to the Fastly service.
Follow these steps to process the subdomain within your Adobe Commerce on cloud infrastructure project:
After performing the steps for subdomain configuration, you must also take these steps to validate your production domain for the SSL certificate:
Using the subdomain allows you to perform a “soft launch” of your store in the future – since such launch only requires updating the corresponding DNS settings.
In our support knowledge base:
In our developer documentation: