AEMaaCS CDN config tips | Community
Skip to main content
shrutid56001193
shrutid56001193
Level 2
March 3, 2026

AEMaaCS CDN config tips

  • March 3, 2026
  • 1 reply
  • 22 views

Hey everyone,

 

Sharing some cdn configs tricks - that I discovered while working on AEM as a cloud service projects - 

🔐 Basic auth at CDN level  - we all know it - but how to exclude for a certain domain? 
🌍 Geolocation-based reverse proxy routing
🚀 Supporting phased country rollouts without DNS changes

Curious to know — are you using origin selectors creatively in your projects?

👉 Securing and Routing Traffic in AEMaaCS Using CDN Configs

      1 reply

      kautuk_sahni
      Community Manager
      kautuk_sahniCommunity Manager
      Community Manager
      March 12, 2026

      Thanks for sharing these practical AEMaaCS CDN configuration tips, especially around basic auth exclusions, geolocation-based routing, and phased country rollouts without DNS changes. These are real-world challenges many teams face when working with AEM as a Cloud Service.

      In your experience, what trade-offs have you seen when using origin selectors for traffic routing or rollout strategies? Would love to hear more about how this approach has worked in your projects.

      Kautuk Sahni
      shrutid56001193
      shrutid56001193Author
      Level 2
      March 14, 2026

      Good question, ​@kautuk_sahni . In my experience, origin selectors are very useful for adding flexibility at the CDN layer — especially for phased rollouts, regional routing, or temporary migration scenarios where you want to avoid DNS changes or application redeployments.

      The main trade-off is complexity. As routing rules grow, it can become harder to reason about request paths and debug issues since part of the logic sits outside AEM in the CDN configuration.

      I’ve found they work best when used deliberately for specific rollout or routing scenarios, while keeping the rule set minimal and well documented.

      https://www.shrutidamle.com/
        Terms & ConditionsAccessibility statement

        Loading footer...