b2c-ecdn_skill

Overview

This skill manages B2C Commerce eCDN (embedded CDN) settings using the b2c CLI. It provides commands to list and create CDN zones, purge caches, manage certificates, configure WAF and firewall rules, and control performance and security features. Use it when you need programmatic control over CDN behavior for a B2C Commerce tenant.

How this skill works

The skill wraps the b2c CLI ecdn topic to call B2C Commerce eCDN APIs using OAuth credentials scoped for cdn-zones operations. It inspects and modifies zone configuration, certificates, cache entries, WAF and firewall rules, rate limiting, logpush jobs, Page Shield policies, MRT routing, mTLS certificates, cipher suites, and origin header settings. Commands accept a tenant ID and a zone identifier (ID or name) and output JSON or human-readable text.

When to use it

• When you need to purge cached content for specific paths, tags, or an entire zone.
• When adding or validating custom TLS certificates for a storefront hostname.
• When configuring or migrating WAF rules, firewall rules, or rate limiting for a zone.
• When creating or updating CDN zones and origin hostnames for new storefronts.
• When setting up logpush destinations, Page Shield policies, or MRT routing.

Best practices

• Use OAuth credentials with the correct scope: sfcc.cdn-zones for read and sfcc.cdn-zones.rw for write actions.
• Test changes in a staging tenant before applying to production zones, especially WAF and firewall rules.
• Use --json for scripting and CI pipelines to parse outputs reliably.
• Specify tenant ID via SFCC_TENANT_ID env var or the --tenant-id flag to avoid accidental changes.
• Purge cache selectively (paths or tags) instead of purging everything unless necessary.

Example use cases

• Purge product and category pages after a catalog update to ensure customers see fresh data.
• Add and validate a new SSL certificate for www.example.com on a storefront zone.
• Enable a WAF v2 ruleset and migrate a zone from WAF v1 to v2 for improved protection.
• Create a logpush job to send HTTP logs to an S3 bucket for analytics and debugging.
• Create an MRT ruleset to route traffic to a Managed Runtime storefront for a progressive web app.