Akamai integration with AEMaaCS | Community
Skip to main content
April 17, 2025

Akamai integration with AEMaaCS

  • April 17, 2025
  • 2 replies
  • 1457 views

Hi,

My requirement is to use Akamai as CDN for my AEMaaCS project.
Followed this documentation from Adobe CDN in AEM as a Cloud Service | Adobe Experience Manager.

Akamai we configured as per the sample vendor configurations.
I created a edge key and deployed it through cdn.yaml file (attached screenshot) as a secret type environment variable. Same key we are passing as X-AEM-Edge-Key header from Akamai.

1) When I try to run the curl command  << curl https://publish-p<PROGRAM_ID>-e<ENV-ID>.adobeaemcloud.com -v --header "X-Forwarded-Host: example.com" --header "X-AEM-Edge-Key: <PROVIDED_EDGE_KEY>" --header "x-aem-debug: edge=true" >>
the response is 302, and the X-Forwarded-Host expected value in response header is the domain, but it is returning publisher url (in 'x-aem-debug' response header).

2) When I try to run the curl command  << curl https://publish-p<PROGRAM_ID>-e<ENV-ID>.adobeaemcloud.com/content/example-homepage.html -v --header "X-Forwarded-Host: example.com" --header "X-AEM-Edge-Key: <PROVIDED_EDGE_KEY>" --header "x-aem-debug: edge=true" >>


the response is 200. This url is the publish url for the homepage of the project(with /content path).
and X-Forwarded-Host expected value in response header is the domain, but it is returning publisher url (in 'x-aem-debug' response header).

3) When I try to run the curl command  << curl https://example.com -v --header "X-Forwarded-Host: example.com" --header "X-AEM-Edge-Key: <PROVIDED_EDGE_KEY>" --header "x-aem-debug: edge=true" >>
the response is 200. Here, X-Forwarded-Host is returning example.com , and host=example.com (in 'x-aem-debug' response header)

What is the problem happening in here, am I missing any steps?
Or is the Akamai configuration wrong?
DNS I am yet to configure, to point the domain to Akamai edge server instead of publish url.
Am I testing the connectivity correct? Please guide me through this issue.

Thanks,
Ranjith

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

2 replies

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

Hi @ranjithr1,

did you create a farm file in the Dispatcher configuration with example.com domain listed under /virtualhosts?

Check the Dispatcher logs to make sure your request is hitting the correct farm.

Something seems to be misconfigured on your end, as we use Akamai and the same approach of passing edge key and the forwarded host to the Dispatcher.

 

BR,

Daniel

RanjithR1Author
April 22, 2025

Hi @daniel-strmecki 

During troubleshooting, allowed X-Forwarded-Host header in clientheaders,  DispatcherUseForwardedHost - Set to On.

Curl command is returning 302 still, and the X-Forwarded-Host response header in aem-debug, is showing the publish url, not the domain.

Is testing through the curl command correct way? (as shown in documentation)
Or should we point our domain dns to akamai edge server and test like that?

daniel-strmecki
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
April 22, 2025

Hi @ranjithr1,

If CURL is returning 302, check if you have a redirect to the homepage, like /global/en, in that case, this is expected. Try to add the correct page path to your request, for example:

curl -I https://publish-pXXXX-eXXXX.adobeaemcloud.com/global/en -H "X-Forwarded-Host: my-domain.com" -H "X-Edge-Key: XXXXXXXXX" -H "x-aem-debug: edge=true"

In my case the x-aem-debug shows: host=publish-pXXXX-eXXXX.adobeaemcloud.com,x-forwarded-host=my-domain.com

I suggest you check the Dispatcher logs with DEBUG level.

 

Good luck,

Daniel

 

kautuk_sahni
Community Manager
Community Manager
July 9, 2025

@ranjithr1 Just checking in — were you able to resolve your issue?
We’d love to hear how things worked out. If the suggestions above helped, marking a response as correct can guide others with similar questions. And if you found another solution, feel free to share it — your insights could really benefit the community. Thanks again for being part of the conversation!

Kautuk Sahni