Fastly CDN module for Magento 2
Fastly services for Adobe Commerce on cloud infrastructure use the Fastly CDN module for Magento 2 installed in the following environments: Pro Staging and Production, Starter Production (master
branch).
On initial provisioning or upgrade of your Adobe Commerce project, Adobe installs the latest version of the Fastly CDN module in your Staging and Production environments. When Fastly releases module updates, you receive notifications in the Admin for your environments. Adobe recommends that you update your environments to use the latest release. See Upgrade Fastly.
Fastly service account and credentials
Adobe Commerce on cloud infrastructure projects are not given a dedicated Fastly account. The Fastly service is managed in a centralized account registered to Adobe, and the management dashboard is only accessible to the Cloud Support team.
Instead, each Staging and Production environment has unique Fastly credentials (API token and service ID) to configure and manage Fastly services from the Commerce Admin. The Fastly API is available for performing advanced management of the Fastly service, which will require the credentials to submit those requests.
During project provisioning, Adobe adds your project to the Fastly service account for Adobe Commerce on cloud infrastructure and adds the Fastly credentials to the configuration for the Staging and Production environments. See Get Fastly credentials.
Change Fastly API token
Submit an Adobe Commerce Support ticket to change the Fastly API token credential. When you receive the new token, update your Staging or Production environment to use the new token.
To change the Fastly API token credential:
-
Submit an Adobe Commerce Support ticket requesting new Fastly API credentials.
Include your Adobe Commerce on cloud infrastructure project ID and the environments that require a new credential.
-
After you receive the new API token, update the API token value in the Fastly credentials configuration in the Admin or from the Cloud Console environment variables.
-
After you update the credential, submit an Adobe Commerce Support ticket to delete the old API token.
Multiple Fastly accounts and assigned domains
Fastly only allows you to assign an apex domain and associated subdomains to one Fastly service and account. If you have an existing Fastly account that links the same apex and subdomains used for your Adobe Commerce site, you have the following options:
-
Remove the apex and subdomains from the existing account before requesting Fastly service credentials for your Adobe Commerce on cloud infrastructure project environments. See Working with Domains in the Fastly documentation.
Use this option to link the apex domain and all subdomains to the Fastly service account for Adobe Commerce on cloud infrastructure.
-
Submit an Adobe Commerce support ticket to request domain delegation so that apex and subdomains can be linked to different accounts.
Use this option if you have an apex domain that has multiple subdomains for Adobe Commerce and non-Adobe Commerce sites, and you want to link these subdomains to different Fastly accounts.
Request domain delegation
Scenario 1:
The apex domain (testweb.com
and www.testweb.com
) is linked to an existing Fastly account. You have an Adobe Commerce on cloud infrastructure project configured with the following subdomains: mcstaging.testweb.com
and mcprod.testweb.com
. You do not want to move the apex domain to the Fastly service account for Adobe Commerce on cloud infrastructure.
Submit a Fastly support ticket requesting that the subdomains be delegated from the existing Fastly account to the Fastly account for Adobe Commerce on cloud infrastructure. Include your Adobe Commerce project ID in the ticket.
After the delegation is complete, your project subdomains can be added to the Fastly service account for Adobe Commerce on cloud infrastructure. See Get Fastly credentials.
Scenario 2:
The apex domain (testweb.com
and www.testweb.com
) is linked to the Adobe Commerce on cloud infrastructure Fastly service account. You want to manage Fastly services for the service.testweb.com
and product-updates.testweb.com
subdomains from a different Fastly account.
Submit an Adobe Commerce Support ticket requesting that the subdomains be delegated from the Adobe Commerce on cloud infrastructure Fastly service account to the Fastly account. Include the service ID for the Fastly account in the ticket.
DDoS protection
DDOS protection is built in to the Fastly CDN service. Once you have enabled Fastly services for your Adobe Commerce sites, Fastly filters all web and admin traffic to detect and block potential attacks.
-
For attacks targeting layer 3 or 4, the Fastly service filters out traffic based on port and protocol, inspecting only HTTP or HTTPS requests. ICMP, UDP, and other network-initiated attacks are dropped at our network edge. This includes reflection and amplification attacks, which use UDP services like SSDP or NTP. By providing this level of protection, we effectively block multiple common attacks like Ping of Death, Smurf attacks, and other ICMP-based floods.
Fastly manages TCP level attacks at the cache layer. This strategy provides the necessary scale and context per client to deal with a SYN flood attack and its many variants, including TCP stack, resource attacks, and TLS attacks within Fastly systems.
-
Fastly also provides protection against Layer 7 attacks. If your store is experiencing performance issues and you suspect a Layer 7 DDoS attack, submit an Adobe Commerce Support ticket. Adobe can create and apply custom rules to the Fastly service to inspect for and filter out malicious requests based on header, payload, or a combination of attributes that identify the attack traffic. See Checking for DDoS attacks and How to block malicious traffic in the Adobe Commerce Help Center.