Expand my Community achievements bar.

Submissions are now open for the 2026 Adobe Experience Maker Awards.

AEMaaCS Dedicated Egress IP not working as expected

Avatar

Level 3

Hi,

We have enabled dedicated egress for our AEMaaCS program but when we are making 3rd party REST API calls (Boomi) from AEM server side (OSGi services) the client IP in Azure Front door which is in front of Boomi does not match with AEMaaCS dedicated egress IP as a result we see http status 502 with mesasage something like "Azure Front door cannot connect to the origin server." We noticed that client IP is changing frequently.

Command nslookup p<Program ID>.external.adobeaemcloud.com - gives us the correct dedicated egress IP which has been whitelisted in Azure Front door of target/Boomi.

Can anyone help us with a solution for this issue? Do we need to change the implementation of HttpClient connection call?

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

0 Replies