To use Fastly on your Staging and Production environments with Magento Commerce (Cloud), you must create and point the corresponding CNAME aliases or domain names to one of the following:
- Fastly CNAME hostname, or
- all four Fastly Anycast IP addresses using A records
Fastly CNAME and Anycast IP's
Fastly CNAME hostname:
prod.magentocloud.map.fastly.netFastly Anycast IP addresses:
151.101.1.124
151.101.65.124
151.101.129.124
151.101.193.124
Staging environment (Pro plan only)
You may add a subdomain and use a short URL (like staging.<your_domain_name>.com, which is more convenient for real-life testing scenarios) instead of the long origin URL of your Staging environment. Such being the case, you must update your DNS record to include the Staging subdomain.
To configure the DNS record for your Staging environment to use Fastly, follow these steps:
- Add the Staging subdomain to your DNS settings.
- Point the new Staging subdomain to Fastly using Fastly's CNAME or Anycast IP's.
- Add the DNS TXT record for subdomain validation.
- Submit a support ticket requesting to validate your SSL certificate.
- Change the Magento Base URL's.
Naming convention for Staging subdomain
The usual naming convention is: staging.<your_domain_name>.com.
Any subdomain names you are using in your Magento Commerce (Cloud) Project must match the ones specified in your Onboarding UI.
DNS TXT record for SSL certificate
You are supposed to obtain the corresponding DNS TXT record for your apex domain name after your onboarding meeting. The corresponding SSL certificate will cover all first-level subdomains (like staging.<your_domain_name>.com, prod.<your_domai_name>.com).
If you cannot find the DNS TXT record, submit a support ticket requesting it. In the ticket, specify the production domain name URL.
You must submit a support ticket requesting to validate your SSL certificate once you add the TXT record to your DNS settings.
Subdomains are not available on Staging for Starter plan
The ability to add subdomains on your Staging environment is only available for the Pro plan users. For the Starter plan, you may only test your Staging site using the origin URL.
Production environment
To configure your live DNS record to use Fastly, follow these steps:
- Add the new production domain name to your DNS settings (if the domain name has not been added already).
- Point the production domain to Fastly using Fastly's CNAME or Anycast IP's.
- Add the DNS TXT record for subdomain validation (optional).
- Submit a support ticket requesting to validate your SSL certificate (optional).
- Change the Magento Base URL's.
SSL validation on Staging and Production
If you have successfully validated the SSL certificate for your Staging domain, you may use the same certificate for your Production domain.
Recommendation: add your Production subdomain to Fastly
We highly recommend requesting that the Production subdomain you are using for pre-launch testing (prod.<your_domain_name>.com) is added to Fastly as well. You may point the Production subdomain to Fastly the same way as for the Staging environment.
If your Production subdomain is added to Fastly, you are able to test your store on the Production environment with Fastly enabled before going live, especially if you are migrating and do not want to use the current (live) domain name for testing purposes on Production.
Using Staging subdomain with your existing Staging domain
If you are already using the same Staging name in your previous Magento development site, create a separate DNS record for your Staging subdomain as a CNAME that points to the prod.magentocloud.map.fastly.net hostname.
To create a hostname that allows you to connect directly to the cluster and bypass Fastly, point your CNAME record to the c.<project_ID>.ent.magento.cloud hostname. Make sure to mention this in your Onboarding UI.
Important notes
Domain names in your Onboarding UI
You can find the DNS information in your Onboarding UI on the DNSSSLCDN tab.
The tab includes the following info:
- your requested domain names, Fastly and origin (with
*.c.<your_client_id>.ent.magento.cloud) - all Fastly Anycast IP addresses and the CNAME alias
If you don't have access to the Onboarding UI, ask your Magento Commerce account owner to grant access.
CNAME to origin domain name to bypass Fastly (not recommended)
You can CNAME your domain names directly to the origin domain name (with *.c.<your_client_id>.ent.magento.cloud) to bypass Fastly. In this case, you need to use your own SSL (TLS) certificate.
However, if you bypass Fastly, we cannot guarantee a satisfactory site performance since Fastly is highly recommended for your Magento Commerce (Cloud) store.
Related documentation
Knowledge Base
- Set up Fastly for Starter plan on Cloud
- Potential blockers for launching on Magento Commerce (Cloud)