Table of Contents


  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

Advanced cluster types

Advanced cluster

Different types of
advanced clusters
are available to enable advanced functionality in mappings and help you choose the infrastructure that best supports your organization's processing requirements.
You can use the following types of
advanced clusters
in your organization:
Fully-managed cluster
A cluster that provides a serverless infrastructure that intelligently scales based on your workload and offers the lowest total cost of ownership for your organization. For more information, see Advanced clusters (fully-managed).
Self-service cluster
A Kubernetes cluster that your organization runs and you reuse to run mappings. The Kubernetes cluster can run on either AWS or Microsoft Azure. For more information, see Self-service clusters.
Local cluster
A simple, single-node cluster that you can start on the Secure Agent machine. You can use a local cluster to quickly onboard projects for advanced use cases. For more information, see Local clusters.
Advanced cluster
in a serverless runtime environment
If your organization uses AWS, you can create a serverless runtime environment that includes an
advanced cluster
for your organization to use. For more information, see
Runtime Environments
All of the
advanced cluster
types are similar with respect to the following areas:
  • Network privacy
  • Communication between the Secure Agent and the cluster, among Kubernetes Pods, and between a Kubernetes Pod or the cluster, and the internet
  • Internet access to download Informatica's Docker images and artifacts
  • Access to external data sources, such as sources and targets in data integration mappings
You can restrict Informatica's access to your cloud environment by configuring sensitive resources like cloud roles and security groups according to your organization's security guidelines. For example, in a self-service cluster, Kubernetes resources might be shared between Informatica and non-Informatica applications and users. You can create your own Kubernetes roles or cluster roles to restrict Informatica's access to the cluster and specify the resources that Informatica can interact with.


We’d like to hear from you!