Fastly services overview

Content Delivery Network (CDN)—Varnish-based service that caches your site pages, assets, CSS, and more in backend data centers you set up. As customers access your site and stores, the requests hit Fastly to load cached pages faster. The CDN service provides the following features:

Cache management—Cache your site pages, assets, CSS, and more in back-end data centers that you set up to reduce bandwidth load and costs

• Use Fastly custom VCL snippets (Varnish 2.1 compliant) to modify how caching responds to requests

• Set up GeoIP service support

• Force unencrypted requests over to TLS

• Customize Fastly timeout settings to prevent 503 responses on bulk operation requests

• Create custom error response pages

Security—After you enable Fastly services for Adobe Commerce sites, additional security features are available to protect your sites and network:

• Web Application Firewall (WAF)—Managed web application firewall service that provides PCI-compliant protection to block malicious traffic before it can damage your production Adobe Commerce on cloud infrastructure sites and network. The WAF service is available on Pro and Starter Production environments only.

• Distributed Denial of Service (DDoS) protection—Built-in DDoS protection against common attacks like Ping of Death, Smurf attacks, and other ICMP-based flood attacks.

• SSL/TLS certificates—The Fastly service requires an SSL/TLS certificate to serve secure traffic over HTTPS.

  Adobe Commerce provides a Domain-validated Let’s Encrypt SSL/TLS certificate for each Staging and Production environment. Adobe Commerce completes domain validation and certificate provisioning during the Fastly set up process.

Origin cloaking—Prevents traffic from bypassing the Fastly WAF and hides the IP addresses of your origin servers to protect them from direct access and DDoS attacks.

Origin cloaking is enabled by default on Adobe Commerce on cloud infrastructure Pro Production projects. To enable origin cloaking on Adobe Commerce on cloud infrastructure Starter Production projects, submit an Adobe Commerce Support ticket. If you have traffic that does not require caching, you can customize the Fastly service configuration to allow requests to bypass the Fastly cache.

Image optimization—Offloads image processing and resizing load to the Fastly service so that servers can process orders and conversions more efficiently.

Fastly CDN and WAF logs—For Adobe Commerce on cloud infrastructure Pro projects, you can use the New Relic Logs service to review and analyze Fastly CDN and WAF log data.

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.

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.