How to get AEMaaCS Author IP address for whitelisting with another API?

[konstantyn_diachenko]

Hi everyone,

I'm working on a setup where my AEMaaCS author instance makes API calls to serviceA. However, the API for serviceA is restricted and can only be accessed by white-listed IP addresses. I need to figure out how to obtain the public IP address of my AEMaaCS author instances so that I can white-list it in serviceA.

I executed ping command to get IP for my author, but it's Fastly IP address. 

What is the best way to get the public IP address of AEMaaCS author server to provide it for white-listing?

Any help or best practices for this setup would be greatly appreciated!

[daniel-strmecki · Accepted solution]

Hi @konstantyn_diachenko,

you will need to contact Adobe support to find our the IP range of your author instances. Keep it mind author tier also scales in AEMaaCS so it will never be one single public IP you can whitelist.

I would suggest to switch to domain-based whitelisting, token-based authentication or a static proxy with a static IP address.

Good luck,

Daniel

[konstantyn_diachenko]

Hi @daniel-strmecki , thank you, you confirmed my biggest fears about static IP. 

[Jörg_Hoh]

This is the not the correct answer, as this IP range might change without further notice. If you need your AEM environment make calls to an external service, and these requests must come from a specific IP/small set of IPs, then use the Dedicated Egress IP solution, as correctly suggested by @Mahedi_Sabuj below.

[Mahedi_Sabuj]

Hi @konstantyn_diachenko,

We have raised Adobe support ticket last month regarding same topic. Support team confirmed - Cloud Env IP range is large and is not shared for whitelisting. You need to set Advanced Networking. Dedicated Egress IP would be the right fit for the use case you mentioned. Please review [1]

It won't have any performance effect, and the same dedicated IP is applied for all environments in your program.

[1] - https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/security/configu...