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

Validating the configuration

Validating the configuration

You can validate the information needed to create or update an
advanced configuration
before you save the configuration properties.
The validation process performs the following validations:
  • You have provided the necessary information on the configuration page.
  • The information you provided is valid or in the correct format. For example, the runtime environment shouldn't be associated with another
    advanced configuration
    .
If you encounter errors related to context keys when you validate an
advanced configuration
, then add key
ccs.k8s.policy.context.key
to the runtime property in the
advanced configuration
. You can use the following value structure to add the context keys:
"ContextKeyName-'keyName1',ContextKeyValues-'keyValue1',ContextKeyType-(string|stringList|numeric|numericList|boolean|booleanList|ip|ipList|binary|binaryList|date|dateList)&infaContextKeyName-'keyName2',ContextKeyValues-'keyValue2',ContextKeyType-(string|stringList|numeric|numericList|boolean|booleanList|ip|ipList|binary|binaryList|date|dateList)"
For example:
ccs.k8s.policy.context.key=ContextKeyName-'aws:username',ContextKeyValues-'kops',ContextKeyType-string&infaContextKeyName-'ec2:ResourceTag/CREATED_BY',ContextKeyValues-'SFA-TDS',ContextKeyType-string
For more information about context keys, contact Informatica Global Customer Support.

0 COMMENTS

We’d like to hear from you!
Alessio Giordani - February 18, 2026

Hello Documentation team,

It would be good write a remarks regarding the Cluster Validation that could fails due to lack of privileges on the AWS Policy

i.e. "Check AWS IAM Policy [arn:aws:iam:::role/] because the action [autoscaling:DescribeAutoScalingInstances] to resource [arn:aws:autoscaling:us-west-2::autoScalingGroup:*:autoScalingGroupName/*] is not allowed. There are no matching policy action statements.)"

since currently is not able to validate every possible Policy setup. In fact, implementing the "user-defined master and worker roles" the Cluster Validation Fails but the cluster starts correctly. It is always recommended to run a unit test with a simple mapping (read/write on S3), and check the  ccs-operation.logs.

Not sure if the user guide is appropriate for this remark or better write a KB article and link it here.

Regards,

Alessio

Informatica Documentation Team - February 19, 2026

Thanks for bringing this to our attention, Alessio! We'll investigate and update the documentation in an upcoming release.