Change in pod IP addresses for IICS AP SouthEast1

Version 5

    As part of our continuous infrastructure improvement, Informatica Intelligent Cloud Services is reducing the number of IP addresses needed to be allowed in your company’s firewall. Please find the current list at the bottom for reference that will be replaced with the 4 IP addresses. (2 Primary and 2 DR)


    With the new update, any new node additions in the future will not need additional IP addresses to be allowed on your firewall. This change will be effective as of 16th Nov Early 2022 for your pod.


    Please leave old IP address as-is until further notice.


    The Identity Service and Package Dependency Manager IP addresses are not impacted by this change and should remain allowed.


    Please allow these IP addresses on your organization firewall avoid any service disruption.


    New Primary IP Addresses to be added:


    New DR IP addresses to be added:



    URL to test if the site is accessible:



    Frequently Asked Questions:


    Q: Is my organization impacted?

    A: If your organization needed to allow specific IP addresses for outbound communication in the past to access IICS, then you will need to allow these new IP addresses as well. These 2 new IP addresses replace the existing IP address list.

    If you never had to allow IP addresses for outbound communication on port 443 or if you allow traffic based on domain names (* and * then NO further action is needed.


    Q: Which IICS POD is impacted by this?

    A:This is applicable for AP SouthEast 1 pod.


    Q: Is there a deadline for making this change?

    A: YES, November 15th.

    The deadline is now moved to a future date, we will communicate soon on the date.


    Q: Why are these IPs needed?      

    A:  These IPs are static and will ensure you do not have to add additional IPs in case IICS needs to scale up with additional nodes.


    Q: What will be the impact of not allowing these additional IP addresses?

    A: There will be service disruption. Secure agent services and UI accessibility via browser will be impacted.


    Q: Do we need to remove IP addresses allowed earlier?

    A: You can remove them from firewall allow list after November 30th 2021.

    Please leave old IP address as-is until further notice.


    Q: How to test connectivity to the new site ?

    A: To test connectivity one can run "curl" or "telnet" from the Secure Agent machine. ("curl" can be also downloaded from: curl - Download )

    Example outputs are below:


    Please run:

    curl -v


    telnet 443


    If connected, the above commands would show the same:


    Curl example output: (Please IGNORE ssl related messages, please ignore "503 Service Unavailable" message)

    curl -v

    * About to connect() to port 443

    *   Trying connected

    * Connected to ( port 443


    Telnet Example output:

    telnet 443


    Connected to (



    Q: Who do we need to work with to allow these IPs?

    A: These IPs are to be allowed on your organization firewall/proxy. Hence, please contact your organization's IT/Network administrators who manage the firewall/proxy configurations.



    Please leave these old IP address as-is until further notice.




    IP Addresses for IICS APSE1 pod (in addition to the APJ instance Identity Service and APJ Package Dependency Manager IP Addresses above)


    Primary IP Addresses

    Disaster Recovery IP Addresses


    Additional primary IPs for APSE1


    New Disaster Recovery IP Addresses