AEM Cloud outbound traffic issue

[EthanRo5]

I have configured a dedicated egress IP address for my AEM as a Cloud Service environment following the Cloud Manager settings. I have enabled the dedicated egress IP with the IP range. However, outbound traffic still does not seem to originate from the dedicated IP address.

What common steps or configurations might I be missing to make this setup work correctly? Are there any specific settings related to port forwarding or non-proxy hosts that need special attention?

Any advice or troubleshooting tips would be appreciated!

For reference, I followed the official Adobe doc here:
https://experienceleague.adobe.com/en/docs/experience-manager-learn/cloud-service/networking/dedicat...

[SantoshSai · Accepted solution]

Hi @EthanRo5,

Please double-check:

1. Cloud Manager configuration:
   Make sure that the dedicated egress IP feature is enabled in your Cloud Manager environment settings. This is a required toggle that activates the egress IP for your environment.

2. cdn.yaml update:
   Verify that you have properly updated the cdn.yaml file with the correct IP address range for your dedicated egress IP. This file controls the CDN configuration and routing rules, so any mismatch here can cause the traffic to not route properly.

3. Port Forwarding and Protocol Handling:

   • Outbound HTTP and HTTPS traffic is routed automatically through the dedicated egress IP once enabled.

   • For non-HTTP/HTTPS traffic (other protocols or ports), you need to explicitly configure port forwarding rules in your Cloud Manager settings to allow those connections to route through the egress IP. If this step is missing, such traffic will not use the dedicated IP.

   • Also, ensure your application or integration respects the non-proxy hosts configuration if applicable.

4. Firewall and External Allowlisting:
   Double-check if your external services are allowlisting the correct dedicated egress IP address range. Sometimes, the external system is still expecting traffic from the old IPs.

If after these checks it still doesn’t work, you might want to raise a support ticket with Adobe since the dedicated egress IP feature involves backend cloud infrastructure that might require assistance.

For complete details, here is the official Adobe documentation that explains the setup and troubleshooting in depth:
https://experienceleague.adobe.com/en/docs/experience-manager-learn/cloud-service/networking/dedicat...

Hope that helps!

[arunpatidar]

Hi @EthanRo5 

Please check https://medium.com/@angadi.saa/aemascs-egress-ip-address-setup-for-outbound-api-call-45ae7e4e0d39 

[EthanRo5]

Thanks @SantoshSai and @arunpatidar  the problem was with the missing configuration around the egress IP allow-list and non-proxy hosts- as @SantoshSai mentioned.