Skip Ribbon Commands
Skip to main content
Navigate Up
Sign In

Quick Launch

Average Rating:

facebook Twitter
Email
Print Bookmark Alert me when this article is updated

Feedback

ERROR: "java.lang.IllegalArgumentException: No region provided" when CDI-E mapping fails to start the cluster on AWS​ with the error
Problem Description
CDI-E mapping fails to start the cluster on AWS​ with the following error in ccs-operation.log:

2020-01-01 00:00:00.001 [reqid:iJrova4iny8frhtVmPJUQc] [T:000038] ERROR  : c.i.c.s.c.ClusterComputingService        [CCS_10103] Failed to create cluster [1aaaa11aaaaaaaaa1aaaaa.k8s.local] due to the following error: [java.lang.IllegalArgumentException: No region provided
[java.lang.IllegalArgumentException: No region provided
        at com.amazonaws.AmazonWebServiceClient.setRegion(AmazonWebServiceClient.java:424)
        at com.amazonaws.services.s3.AmazonS3Client.setRegion(AmazonS3Client.java:690)
        at com.amazonaws.client.builder.AwsClientBuilder.setRegion(AwsClientBuilder.java:369)
        at com.amazonaws.client.builder.AwsClientBuilder.configureMutableProperties(AwsClientBuilder.java:337)
        at com.amazonaws.client.builder.AwsSyncClientBuilder.build(AwsSyncClientBuilder.java:46)
        at com.informatica.cloud.service.ccs.aws.AWSUtils.<init>(AWSUtils.java:215)
        at com.informatica.cloud.service.ccs.k8s.aws.kops.KopsClusterOperatorForAWS.<init>(KopsClusterOperatorForAWS.java:130)
        at com.informatica.cloud.service.ccs.k8s.K8sClusterManager.createClusterOperator(K8sClusterManager.java:785)
        at com.informatica.cloud.service.ccs.k8s.K8sClusterManager.initialize(K8sClusterManager.java:609)
        at com.informatica.cloud.service.ccs.k8s.K8sClusterManager.createClusterImpl(K8sClusterManager.java:216)
        at com.informatica.cloud.service.ccs.ClusterManager.createCluster(ClusterManager.java:336)
        at com.informatica.cloud.service.ccs.ClusterComputingService.createCluster(ClusterComputingService.java:238)
        at com.infa.discale.atscaleagent.webapp.mercury.impl.K8ClusterManagerImpl.createCluster(K8ClusterManagerImpl.java:269)
Cause
​The issue occurs when instance profiles are not specified in the Elastic Cluster configuration.

And thus, the AtScale service is unable to retrieve the AWS credentials required for creating the cluster.
Solution
You may follow one of the below approaches:
  • ​If the AWS instance profile is available, provide the same in the Elastic Cluster configuration as shown:
instance_profile.png

  • If you wish to use access key/secret key instead of instance profiles, perform the below steps on the agent node.
a) Login to the Informatica agent machine as the user which starts the Informatica agent services.
b) Create a directory named .aws in home directory of the user.
c) Create the below 2 files in ~/.aws directory and enter the AWS credentials of kops user (secret key and access key) and region details.

~/.aws/credentials

[kops]
aws_access_key_id=<AWS_ACCESS_KEY_OF_KOPS_USER>
aws_secret_access_key=<AWS_SECRET_KEY_OF_KOPS_USER>​

~/.aws/config

[kops]
region=<REGION>
output=json

Ensure to specify the AWS region according to your endpoint. The list of all available endpoints are mentioned in the below link.
https://docs.aws.amazon.com/general/latest/gr/rande.html#regional-endpoints.
Example: us-west-1

d) Save the files.

After these changes, re-run the mapping.
More Information
Note: Make sure that the kops user on AWS has the managed policy IAMFullAccess to create roles for the elastic cluster instances.​
Applies To
Product: Cloud Data Integration
Problem Type: Configuration
User Type: Administrator; Developer
Project Phase: Implement; Configure
Product Version:
Database:
Operating System:
Other Software:

Reference
Attachments
Last Modified Date:9/14/2020 9:12 PMID:632696
People who viewed this also viewed

Feedback

Did this KB document help you?



What can we do to improve this information (2000 or fewer characters)