How do I manage the CDN config for an AEMaaCS setup? | Community
Skip to main content
jayv25585659
jayv25585659
Level 8
April 17, 2025
Solved

How do I manage the CDN config for an AEMaaCS setup?

  • April 17, 2025
  • 1 reply
  • 744 views

as above. from what I can see, I have no direct access to the AWS console. I'm guessing the configuration is done via some sort of configuration in my code base?

 

In a previous role (which was an AMS setup), I can access the AWS/Cloudfront console with the help of our AMS rep.

 

can you please link me to some guide/tutorial?

 

Thank you.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by SantoshSai

@daniel-strmecki That's right forgot to add more details:

Adobe has introduced a CDN Config Pipeline to provide limited but powerful configurability over the CDN layer. While customers can’t access the CDN infrastructure directly, they can define CDN behavior declaratively through YAML configuration files (cdn.yaml) checked into Git and deployed via the Cloud Manager CDN pipeline.

With this approach, you can control:

  • Header manipulation (e.g., injecting X-AEM-Edge-Key)

  • Authentication via edge keys

  • Redirects and rewrites

  • Caching and routing logic

So in short: you don’t need AWS or CloudFront console access — but you can influence CDN behavior using Adobe’s configuration-based approach, without having to go through support for every change.

1 reply

SantoshSai
Community Advisor
SantoshSaiCommunity Advisor
Community Advisor
April 17, 2025

Hi @jayv25585659,

In AEM as a Cloud Service (AEMaaCS), CDN configuration is not managed directly by customers, unlike in AMS setups where CloudFront access might be available via an AMS rep. Instead, the CDN layer (typically Akamai) is fully managed by Adobe. Customers do not configure the CDN through the AWS console or through their AEM project code. Instead, CDN-related changes — such as caching rules, redirects, or header manipulations — are handled by Adobe via support requests. You can control some behavior through Dispatcher configurations, but edge CDN logic must go through Adobe’s support channels.

For more details kindly refer: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/content-delivery/cdn

 

Hope that helps!

Regards,
Santosh

Santosh Sai
daniel-strmecki
Community Advisor and Adobe Champion
daniel-strmeckiCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
April 17, 2025

Well, not exactly. Some CDN configurations can be controlled by developers and deployed to AEMaaCS using a Config pipeline. Please check the following docs and examples to see what is possible to configure:

 

Good luck,

Daniel

    SantoshSai
    Community Advisor
    SantoshSaiCommunity AdvisorAccepted solution
    Community Advisor
    April 17, 2025

    @daniel-strmecki That's right forgot to add more details:

    Adobe has introduced a CDN Config Pipeline to provide limited but powerful configurability over the CDN layer. While customers can’t access the CDN infrastructure directly, they can define CDN behavior declaratively through YAML configuration files (cdn.yaml) checked into Git and deployed via the Cloud Manager CDN pipeline.

    With this approach, you can control:

    • Header manipulation (e.g., injecting X-AEM-Edge-Key)

    • Authentication via edge keys

    • Redirects and rewrites

    • Caching and routing logic

    So in short: you don’t need AWS or CloudFront console access — but you can influence CDN behavior using Adobe’s configuration-based approach, without having to go through support for every change.

    Santosh Sai
      Terms & ConditionsAccessibility statement

      Loading footer...