Fastly is required for Cloud for Adobe Commerce, and is used in Staging and Production environments. It works with Varnish to provide fast caching capabilities and a Content Delivery Network (CDN) for static assets. Fastly also provides a Web Application Firewall (WAF) to secure your site and Cloud infrastructure. You must route all incoming site traffic through Fastly to protect your site and Cloud infrastructure from malicious traffic and attacks.
Fastly is not available in Integration environments.
Complete the following steps to enable, configure, and test Fastly early in your site development process to enable secure access to your site.
- Get Fastly credentials for Staging and Production environments
- Enable Fastly CDN caching
- Upload Fastly VCL snippets
- Update DNS configuration to route traffic to the Fastly service
- Test Fastly caching
After you enable and verify that Fastly works with the default settings, you can customize cache configuration settings and enable additional options such as image optimization, edge modules, and custom VCL code. See Customize cache configuration.
Get Fastly credentials
During project provisioning, Magento adds your project to the Fastly service account for Cloud for Adobe Commerce and creates Fastly account credentials for the Starter
master and Pro Staging and Production environments. Each environment has unique credentials.
You need the Fastly credentials to configure Fastly CDN services from the Magento Admin UI and to submit Fastly API requests.
With Cloud for Adobe Commerce, you cannot access the Fastly Admin UI directly. You must use the Magento Admin UI to review and update the Fastly configuration for your environments. If you cannot resolve an issue using the Fastly capabilities in the Magento Admin UI, submit a Magento Support ticket.
Use the following methods to find and save the Fastly service ID and API token for your environment:
To view your Fastly credentials:
IaaS-mounted shared directory—On Pro projects, use SSH to connect to your server and get the Fastly credentials from the
/mnt/shared/fastly_tokens.txtfile. Staging and Production environments have unique credentials. You must get the credentials for each environment.
Local workspace—From the command line, use the Magento Cloud CLI to list and review Fastly environment variables.
magento-cloud variable:get -e <environment ID>
Project Web UI—Check the following environment variables in the Environment configuration variables section.
If you cannot find the Fastly credentials for the Staging or Production environments, contact your Magento Customer Technical Advisor (CTA).
Enable Fastly caching
Fastly credentials for Cloud for Adobe Commerce Staging and Production environments
To enable Fastly CDN caching in Staging and Production:
Log in to the Magento Admin UI.
Click Stores > Settings > Configuration > Advanced > System and expand Full Page Cache.
In the Caching Application section, remove the selection from Use system value, and then select Fastly CDN from the drop-down list.
Expand Fastly Configuration and choose caching options.
After configuring the caching options, click Save Config at the top of the page.
Clear the cache according to the notification.
Navigate back to Stores > Settings > Configuration > Advanced > System > Fastly Configuration to continue configuring Fastly.
Test the Fastly credentials
On the Magento Admin UI, navigate to Stores > Settings > Configuration > Advanced > System > Fastly Configuration.
If needed, add the Fastly service ID and API token values for your project environment.
Ignore the link to create a Fastly API token. Use the Fastly credentials (Service ID and API token) that Magento provided.
Click Test credentials.
If the test succeeds, click Save Config, and then clear the cache.
If the test fails, verify that the correct service ID and API token values match the credentials for the current environment.
If the test fails again, submit a support ticket or contact your Customer Technical Advisor (CTA). For Pro projects, include the URLs for your Production and Staging sites. For Starter projects, include the URLs for your
Masterand Staging site.
If you need to change the Fastly API token credential for a Staging or Production environment, see Change Fastly credentials.
Upload VCL to Fastly
After you enable the Fastly module, upload the default VCL code to the Fastly servers. This code provides a series of VCL snippets that specify the configuration settings to enable caching and other Fastly CDN services for your Cloud for Adobe Commerce.
Fastly caching services do not work until you complete the initial upload of the Fastly VCL code for the Staging and Production sites.
To upload the Fastly VCL:
In the Fastly Configuration section, click Upload VCL to Fastly as the following figure shows.
After the upload completes, refresh the cache according to the notification at the top of the page.
Provision SSL/TLS certificates
Magento provides a Domain-Validated Let’s Encrypt SSL/TLS certificate to serve secure HTTPS traffic from Fastly. Magento provides one certificate for each Pro Production, Staging, and Starter Production environment to secure all domains in that environment.
You can provide your own TLS/SSL certificate instead of using the Let’s Encrypt certificate provided by Magento. However, this process requires additional work to set up and maintain. To choose this option, submit a Magento Support ticket or work with your CTA to add custom hosted certificates to your Cloud environments.
To enable the SSL/TLS certificates for your environments, Magento automation completes the following steps:
- Validates domain ownership
- Provisions a Let’s Encrypt SSL/TLS certificate that covers specified top-level and subdomains for your Magento stores
- Uploads the certificate to the Cloud environment when the site is live
This automation requires you to update the DNS configuration for your site to supply domain validation information. Use one of the following methods:
- DNS validation–For live sites, update your DNS configuration with CNAME records that point to the Fastly service
ACME challenge CNAME records–Update your DNS configuration with ACME challenge CNAME records provided by Magento for each domain in your environment
If you have a Production domain that is not active yet, use the ACME challenge CNAME records for domain validation. Adding the records to your DNS configuration early allows Magento to provision the SSL/TLS certificate with the correct domains before site launch.
When domain validation completes, Magento provisions the Let’s Encrypt TLS/SSL certificate, and uploads it to live Staging or Production environments. This process can take up to 12 hours. We recommend that you complete the DNS configuration updates several days in advance to prevent delays in site development and site launch.
Update DNS configuration with development settings
During the initial Fastly setup process, you can use the following URLs to configure and test Fastly caching in Staging and Production environments:
- Pro projects:
- Starter projects:
You cannot specify a custom domain for a non-production environment in Starter projects.
These are the default pre-production URLs available as soon as your project is provisioned. The value for
"your-domain" is the domain name you specified during the onboarding process.
You must update your DNS configuration to route traffic from your store URLs to the Fastly service. When you update the configuration, Magento automatically provisions the required SSL/TLS certificates and uploads them to your Cloud environments. This provisioning can take up to 12 hours.
When you are ready to launch your Production site, you must update the DNS configuration again to point your production domains to the Fastly service and complete additional configuration tasks. See Launch checklist.
- Enable the Fastly module.
- Upload the default Fastly VCL code.
- Provide a list of top-level and subdomains for each environment to your Customer Technical Advisor (CTA) or submit them in a Magento Support ticket.
- Wait for confirmation that the specified domains have been added to your Cloud environments.
- On Starter projects, add the domains to your Fastly service configuration. See Manage domains.
- For information about updating the DNS configuration, check with your DNS registrar for the correct method for your domain service.
To update your DNS configuration for development:
Add CNAME records to point pre-production URLs to the Fastly service:
prod.magentocloud.map.fastly.net, for example:
Domain or Subdomain CNAME mcprod.your-domain.com prod.magentocloud.map.fastly.net mcstaging.your-domain.com prod.magentocloud.map.fastly.net
When the CNAME records are live, Magento provisions certificates and uploads the SSL/TLS certificates.
If you plan to use apex domains (
your-domain.com) for your Production site, you must configure DNS address records (A records) to point to the Fastly server IP addresses. See Update DNS configuration with production settings.
Add ACME challenge CNAME records for domain validation and pre-provisioning of Production SSL/TLS certificates, for example:
Domain or Subdomain CNAME _acme-challenge.your-domain.com 0123456789abcdef.validation.magento.cloud _acme-challenge.www.your-domain.com 9573186429stuvwx.validation.magento.com _acme-challenge.mystore.your-domain.com 1234567898zxywvu.validation.magento.cloud _acme-challenge.subdomain.your-domain.com 1098765743lmnopq.validation.magento.cloud
After adding the CNAME records, Magento validates the domains and provisions the SSL/TLS certificate for the environment. When you update the DNS configuration to route traffic from these domains to the Fastly service, Magento uploads the certificate to the environment.
Update the Magento Base URL.
Use SSH to log in to the Production environment.
Use the Magento CLI to change the base URL for your store.
php bin/magento setup:store-config:set --base-url="https://mcstaging.your-domain.com/"
As an alternative to using the Magento CLI, you can update the Base URL from the Magento Admin.
Restart web browser.
Test your website.
Test Fastly caching
After you complete the DNS configuration changes, use the cURL command-line tool to verify that Fastly cache is working.
To check the response headers:
In a terminal, use the following
curlcommand to test your live site URL:
curl -vo /dev/null -H Fastly-Debug:1 https://<live-URL>
If you have not set a static route or completed the DNS configuration for the domains on your live site, use the
--resolveflag, which bypasses DNS name resolution.
curl -vo /dev/null -H Fastly-Debug:1 --resolve <live-URL-hostname>:443:<live-IP-address>
In the response, verify the headers to ensure that Fastly is working. You should see following unique headers in the response:
< Fastly-Magento-VCL-Uploaded: yes < X-Cache: HIT, MISS
If the headers do not have the correct values, see Resolve errors found in the response headers for troubleshooting help.
Upgrade the Fastly module
Fastly updates the Fastly CDN for Magento 2 module to resolve issues, increase performance, and provide new features. We recommend that you update the Fastly module in your Staging and Production environments to the latest version.
After you update the module, you must upload the VCL code to apply the changes to the Fastly service configuration.
To check the version of Fastly CDN module for Magento 2:
Change to the root directory of your Cloud environment.
Use Composer to check the installed version.
composer show *fastly*
If the latest releaseis not installed, complete the steps to upgrade the Fastly module.
To upgrade the Fastly module:
In your local Integration environment, use the following module information to upgrade the Fastly module.
module name: fastly/magento2 repository: https://github.com/fastly/fastly-magento2.git
Push your updates to the Staging environment.
Log in to the Magento Admin UI for your Staging environment to upload the VCL code.
Verify Fastly services on the Adobe Commerce Staging site.
After you verify Fastly services on the Staging site, repeat the upgrade process in the Production environment.
If you have added a custom VCL snippet that has the same name as a default snippet, you may need to verify and update those snippets after you upgrade the Fastly module. We do not recommend replacing existing default snippets with custom snippets of the same name. For details on custom VCL, see Custom Fastly VCL snippets.