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

Lists all clusters in a staging directory.
The command uses the following options:
-h | -help
-d | -staging-dir=<cluster-bucket-location-without-prefix-s3://> (AWS environment) or <staging-location-with-prefix-abfs[s]://> (Azure environment)
-azsrg | -azure-storage-resource-group -ac | -azurecpath=azcredfilepath -ct | -cluster-type
The following table describes each option:
Access the help for the command.
Staging directory that is configured in the
advanced configurations
for the clusters.
Use one of the following formats based on your cloud platform:
  • AWS.
    -staging-dir=<bucket name>/<folder name>
    The directory must include at least the bucket name. Do not include the prefix
  • Microsoft Azure.
    -staging-dir=abfs(s)://<file system>@<storage account><folder path>
    Specify the ABFSS protocol if encryption is enabled on the storage location.
Storage resource group that holds the staging storage account and is configured in the
advanced configurations
for the clusters.
Location of the Azure credentials file on the Secure Agent machine which contains APPID, TENANTID, SERVICE PRINCIPAL, SUBSCRIPTION. Not applicable in an AWS environment.
Scripts that contain this option will fail. Use this option in a Microsoft Azure environment only if instructed by Informatica Global Customer Support.
Cluster type for
advanced clusters
in an AWS environment or local clusters in an AWS or Microsoft Azure environment. You can specify local, kubeadm, or kops. By default, the command runs on clusters that are managed by kubeadm. Not applicable in an Azure environment.


We’d like to hear from you!