Index of every page on this site: llms.txt
All skills
proyecto26 avatar

/content-delivery

@228d57d
Run it yourself

This skill should be used when the user asks about a "CDN", "edge caching", "static asset delivery", "media / video delivery", "geo distribution of content" or "edge POP selection", "push vs pull CDN", "cache-control headers" / "TTL for static assets", "origin offload", or "origin shield". It gives the recipe for serving bytes from the edge close to users. Use it whenever a design serves images, video, JS/CSS, or downloads to a wide geography, or the origin is saturated by repeat reads of the same files, even if the user doesn't say "CDN".

Use this Skill: https://skilld.dev/gh/proyecto26/system-design-skills/content-delivery

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesprovidersaws.md

≈483 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Content delivery — AWS

Service mapping

  • CloudFront — the CDN; global PoPs, pull from origin (S3, ALB, or any HTTP origin), Cache-Control/policy-driven TTLs, signed URLs/cookies, and CloudFront Functions / Lambda@Edge for edge logic. The default.
  • Origin Shield — an opt-in regional mid-tier cache for a CloudFront distribution; collapses PoP misses into one origin fetch (→ origin shield option).
  • S3 — the usual static/media origin behind CloudFront; pair via Origin Access Control so the bucket isn't publicly reachable.
  • Route 53 — DNS geo/latency routing to origins or for multi-region (→ load-balancing).
  • No separate "push CDN" product — push is "upload to S3, serve via CloudFront."

When to pick which

CloudFront + S3 for static/media; add Origin Shield when many PoPs hammer a single origin or to blunt stampedes; Lambda@Edge only when you need real request/response manipulation (CloudFront Functions for cheap lightweight header/URL rewrites).

Limits / things that bite (verify against current docs)

  • Cache key is set by cache policies — forwarding all query strings/cookies/ headers tanks hit rate; forward only what varies the response.
  • Invalidations are eventually consistent and the first chunk per month is free, then billed per path — prefer versioned URLs over mass invalidation.
  • Egress (data transfer out) is the dominant cost; pricing tiers vary by region.
  • Lambda@Edge has size/runtime limits and runs in the requesting region — adds latency and complexity vs CloudFront Functions.

Pitfalls

  • Public S3 bucket as origin (use Origin Access Control instead).
  • Forwarding cookies/all query strings in the cache policy → near-zero hit rate.
  • Relying on invalidation for freshness and being surprised by propagation lag.
  • Lock-in: cache policies, Lambda@Edge, and signed-URL formats don't port to other clouds.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts24d3 checks · Risk SAFE
  • Gen Agent Trust Hub24d

    The skill is a comprehensive architectural guide for designing Content Delivery Networks (CDNs). It consists solely of technical documentation and does not contain any executable code, external scripts, or malicious patterns.

  • Socket24d

    No alerts

  • Snyk24d

    Risk: LOW · No issues

Signed by skilld at 228d57d. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 weeks ago.

Activeupdated 4 weeks ago

README badge

README badge for proyecto26/system-design-skills/content-delivery