Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi all,
I am using Talend Open Studio Big Data 7.1 on Windows 7, Jdk 1.8. When using the tDynamoDbOutput component i noticed several times the exception
Exception in component tDynamoDBOutput_3 (LoadLpSampleDynamoChild) com.amazonaws.services.dynamodbv2.model.AmazonDynamoDBException: null (Service: AmazonDynamoDBv2; Status Code: 403; Error Code: null; Request ID: d774cb78-1fe8-11e9-a7b4-b367ba003035)
accessing DynamoDb on AWS. This happened only on our EC2 instances whilst from our development machines everything worked flawlessy. On EC2 i checked the "Inherit credentials from AWS role" since there we use credentials associated with the EC2 instance via IAM Role.
I noticed, after tons of trials and a long debugging session, that tDynamoDbOutput, when the aforementioned settings is not checked generate the following code (just forget for a moment that the password is readable...this could be another issue)
com.amazonaws.auth.AWSCredentials credentials_tDynamoDBOutput_3 = new com.amazonaws.auth.BasicAWSCredentials( "accessKey", "secretKey");
I verified that the same happens when using, for example, tS3List, this generates (correctly) the following
com.amazonaws.auth.AWSCredentials credentials_tS3List_1 = new com.amazonaws.auth.BasicAWSCredentials( "accessKey", decryptedPassword_tS3List_1); com.amazonaws.auth.AWSCredentialsProvider credentialsProvider_tS3List_1 = new com.amazonaws.internal.StaticCredentialsProvider( credentials_tS3List_1);
But the tS3List, when checking the "Inherit..." flag generates the following
com.amazonaws.auth.AWSCredentialsProvider credentialsProvider_tS3Put_3 = new com.amazonaws.auth.InstanceProfileCredentialsProvider();
Instead the tDynamoDbOutput does not change at all its behaviour!
Am i doing something wrong or this is really a possible issue?
EDR
Hello,
Did you leave the access key empty and use the AWS role? Do you have enough permission on DynamoDB?
Best regards
Sabrina
Hi,
I tried leaving the key and secret both empty and filled (of course using roles that last did'nt work). The access to the DynamoDB is possible through aws cli and EC2 role. Even regenerating the source did'nt gave the expected result: the code generated is always the one for the secret+passwd access. Note that changing the secret and password the source code changes accordingly
Thanks,
EDR