Configure the Embedded CDN

The embedded CDN (eCDN) is a geographically distributed network of proxy servers. Configuring the eCDN improves availability and performance, ultimately enhancing the ability to scale your B2C Commerce site (or sites).

Embedded CDN settings are specific to each instance (development, staging, and production) and are managed individually for each. Creating a proxy zone in production doesn’t automatically replicate a corresponding proxy zone in the development or staging instances.

Unlike storefront eCDN settings, Salesforce auto-provisions one SCAPI zone that fronts Salesforce Commerce API (SCAPI) traffic for Development, Staging, and Production. Configure a subset of eCDN controls for that zone from the Production instance. The zone doesn't appear in Business Manager or the CDN API on Development or Staging. See SCAPI Zone Support for B2C Commerce.

Site URL aliases files are instance-specific, so site URL aliases are individually managed for each instance (development, staging, and production). Because each instance has its own aliases file, these files aren't included in data replication. This prevents Site URL Management replication from overwriting URL alias settings on Production with the Staging configuration. Individually edit the site URL aliases on each instance (development, staging, production) to have the same aliases on all instances.

Note Beginning with the 24.4 release, you can configure eCDN for staging in Business Manager.

eCDN on On-Demand Sandboxes (ODS)

Starting with the 26.6 release, Salesforce automatically provisions eCDN for all On-Demand Sandbox (ODS) instances. Every ODS instance receives an eCDN-fronted Default Domain hostname with no configuration required. With the 26.6 default-domain auto-routing, the storefront host for ODS sandboxes changes from .dx to .my, including for already-provisioned sandboxes. Business Manager, WebDAV/code upload, jobs, and the Sandbox API remain on the .dx host—only the storefront moves to .my. Update external integrations (CORS allowed-origins, third-party whitelists, test URLs) to reference the new .my storefront hostname. The .my certificate is Salesforce-managed and publicly trusted, so no TLS reconfiguration is required.

• Storefront hostname format: <instance>.sbx.my.commercecloud.salesforce.com (for example, bldp-001.sbx.my.commercecloud.salesforce.com)
• Business Manager hostname format: <instance>.dx.commercecloud.salesforce.com, proxied through the shared BM zone

ODS eCDN uses a shared zone model: all ODS instances in a realm share one storefront zone and one Business Manager zone. web application firewall (WAF) rules, cache settings, MRT routing rules, host header overrides, and PCI policies configured on the zone apply to all instances in that realm.

After provisioning, the Default Zone appears in Business Manager under Administration | Sites | Embedded CDN Settings. Use the Configure Zones button to manage WAF rules, MRT routing rules, cache settings, host header overrides, and PCI policies for the ODS zone.

Important With the 26.6 eCDN rollout completed across all ODS clusters, existing ODS sandboxes receive the Default Domain automatically — no re-provision required. Existing vanity domains on ODS aren't migrated and remain on the legacy path.

Configure Site URL Aliases for .my Domains

When the storefront host moves to the .my Default Domain (for example, with the 26.6 default-domain auto-routing on ODS), the .my hostname isn't automatically present in your site URL aliases file. If the alias file doesn't include the current .my storefront hostname, generated storefront URLs can point to a different host than the one the browser is on. This mismatch causes cross-origin resource sharing (CORS) errors and breaks features that rely on same-origin requests, such as Page Designer preview.

To resolve this issue, add the .my storefront hostname to the site URL aliases file for each instance that serves the storefront on the Default Domain.

1. In Business Manager, confirm the current .my storefront hostname on the Administration | Sites | Embedded CDN Settings page. The storefront hostname uses the format <instance>.sbx.my.commercecloud.salesforce.com for ODS instances.
2. Open the site URL aliases file. Click App Launcher, and then select Merchant Tools | Site | SEO & Discoverability | Aliases.
3. Add the .my hostname as a hostname entry. Set it as the http-host and https-host in the settings section, or add a hostname rule for it, so that generated storefront URLs use the same host that shoppers and preview tools request. For syntax and examples, see Hostname Aliases for B2C Commerce.
4. Click Apply.

Note Site URL aliases files are instance-specific and aren't included in data replication. Individually edit the site URL aliases on each instance (development, staging, production) so that every instance includes its current storefront hostname.

Tip If external integrations or test automation reference the previous .dx storefront hostname, update them to use the new .my hostname. Also update any CORS allowed-origins lists and third-party service allowlists so that requests to the .my storefront aren't blocked.

1. Default Domain Support for B2C Commerce
   Default Domain provides a Salesforce-managed, eCDN-enabled hostname for each instance (Development, Staging, and Production) so teams can test without manual DNS, custom domain registration, or certificate management.
2. SCAPI Zone Support for B2C Commerce
   A SCAPI zone is the Salesforce-managed eCDN zone that fronts Salesforce Commerce API (SCAPI) traffic. Starting with B2C Commerce 26.10, the Production instance includes a subset of eCDN security controls and analytics for this zone in Business Manager and the CDN API, with no support case required.
3. Create a Zone in B2C Commerce
   The CDN configuration is organized around zones. A zone represents a root or apex domain (for example, example.com). A hostname is a subdomain of a specific zone (for example, www.example.com).
4. Add an SSL Certificate to an eCDN Zone and Configure DNS Mapping
   Add SSL certificates to your hostnames for Zones, and map DNS values from B2C Commerce to your DNS provider account. Add eCDN managed certificates and self-managed certificates.
5. Update an eCDN Zone's Certificate
   When your SSL certificate expires, or you update the hostnames assigned to an SSL certificate, update the certificate in Business Manager for B2C Commerce. Update eCDN managed certificates and self-manged certificates
6. Configure an eCDN Zone for B2C Commerce in Business Manager
   Configure SSL/TLS, certificates, security rules, performance, custom pages, request logs, and Under Attack Mode for an eCDN zone by using the Configure Zone screen in Business Manager.
7. Add Hostnames (Subdomains)
   Subdomains of the same zone can be configured on the same Salesforce B2C Commerce instance, or on different instances of different realms of the same retailer.
8. Migrating Proxy Zones
   USe B2C Commerce Business Manager or the CDN-API to migrate legacy proxy zones. Migrating these zones give you the latest security features, and prevents common hierarchy assignment issues.
9. Configure a Page Shield Policy for the eCDN
   Set up a Page Shield policy to make sure only trusted scripts run on sensitive store pages like cart and checkout. A Page Shield policy helps your B2C Commerce store comply with the Payment Card Industry Data Security Standard (PCI DSS) 4.0 client-side security requirements.
10. Create a Custom Firewall Rule for an eCDN Zone
    Configure a custom firewall rule to control incoming traffic to your B2C Commerce storefront based on specified request parameters.
11. Configure a Host Header Override Rule for an eCDN Zone
    To support a single hostname across multiple realms, create a Host Header Override Rule for B2C Commerce sites that use an external content delivery network (CDN). This rule replaces unique hostnames with a common hostname to maintain the single-hostname setup. If you reuse a hostname, traffic can be unintentionally served from a different realm.
12. Create a Rate Limiting Rule for an eCDN Zone
    Configure a rate limiting rule to specify rate limits for requests that match a particular expression and then perform an action when requests reach those rate limits. Rate limiting rules improve B2C Commerce storefront availability, target specific traffic patterns and combat threats, such as bots.
13. Analyze HTTP and Security Traffic for an eCDN Zone
    To get insights into HTTP traffic and security data, use the eCDN Analytics tab in B2C Commerce Business Manager. The Analytics tab shows the Traffic Analysis timeline chart, top traffic statistics across multiple dimensions, and per-rule activity. Switch between HTTP and Security views to see request traffic or firewall events for the same zone and time range.
14. Storefront Fast Setup – eCDN Step
    The Storefront Next Fast Setup workflow in Business Manager for B2C Commerce automatically provisions an eCDN Default Domain zone as part of storefront creation via the SetupEcdnForStorefront job step.
15. eCDN Cache Rules and Cache Purge
    Cache rules control which content is eligible for caching at the eCDN edge, and cache purge selectively invalidates cached content by tag or path. Both capabilities are available in Business Manager for your B2C Commerce storefront.