Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Ask INFA.

Table of Contents

Search

  1. Preface
  2. Advanced clusters
  3. Setting up AWS
  4. Setting up Google Cloud
  5. Setting up Microsoft Azure
  6. Setting up a self-service cluster
  7. Setting up a local cluster
  8. Advanced configurations
  9. Troubleshooting
  10. Appendix A: Command reference

Advanced Clusters

Advanced Clusters

Prepare for local clusters

Prepare for local clusters

Before you deploy a local cluster, complete preparation steps such as adding domains to your allowlist and disabling your OS firewall. A local cluster runs mappings in advanced mode.
Before you deploy a local cluster, be sure you've completed the following preparation steps:
  • Add the following domains to the outbound allowlist for your local cluster and ensure that they are reachable from the Secure Agent machine:
    artifacthub.informaticacloud.com rhui3.<region>.<cloud>.ce.redhat.com (RHEL 8.x)
    For example:
    rhui3.us-west-2.aws.ce.redhat.com
    The local cluster needs to access these domains to fetch artifacts such as machine images, and to access sources and targets.
    If you use one of the EMEA PODs, also allow this domain:
    artifacthubemea.informaticacloud.com
    EMEA PODs include EM West1, EM Central1 Azure, UK, EM SouthEast 1 Azure, ME Central 2 GCP, EM West 2 GCP.
  • If you are running RHEL 9.x on the Secure Agent machine and you want to use local clusters to run advanced mappings, ensure that Docker version 20 is installed on the Secure Agent machine. You can't use Docker version 21 or higher if you intend to run local clusters.
  • Disable the OS firewall by running this command on the Secure Agent machine:
    sudo systemctl disable firewalld
    Disabling the OS firewall prevents disruption of jobs sent to the local cluster.

0 COMMENTS

We’d like to hear from you!
Coomar Das - October 15, 2025

Hi, for local cluster configuration, would you please make a note on this page to the POD Availability and Networking document, to explicitly say that the IPs and cnames on that document, needs to be allow-listed on the hyperscaler's subnet where the Local Cluster Secure Agent VM will reside?
I know, its a pre-requisite to using IDMC itself, but an explicit note will help customers that may have overlooked this key requirement.

Informatica Documentation Team - October 15, 2025

Thanks for your comment, Coomar! We'll update the documentation in an upcoming release.