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

[jayv25585659]

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.

[SantoshSai]

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/con...

Hope that helps!

Regards,
Santosh

[daniel-strmecki]

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:

• https://adapt.to/2024/schedule/configurability-of-cdn-in-aem-cloud-service
• https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/con...

Good luck,

Daniel

[SantoshSai · Accepted solution]

@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.

[jayv25585659]

Do you know when this feature has been released? Thank you.