You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rather than update the existing documentation, I propose adding DEFAULT_TOPIC_ARN to the global config, which can be overridden in the etl pipeline itself. At least in our case, the same topic_arn is shared within the same mode.
I will add a PR to add this functionality.
The text was updated successfully, but these errors were encountered:
I'm having issues with IAM role permissions and the ability to setup SNS. Here is my stacktrace - raise ETLInputError('Pipeline has errors %s' % self.errors) dataduct.utils.exceptions.ETLInputError: Pipeline has errors [{u'errors': [u"Invalid role 'EMR_DefaultRole' in slot 'role'. Please make sure that the role exist and Data Pipeline has permission to assume the role."], u'id': u'[email protected]'}, {u'errors': [u"Invalid role 'EMR_DefaultRole' in slot 'role'. Please make sure that the role exist and Data Pipeline has permission to assume the role."], u'id': u'[email protected]'}] Any help would be appreciated.
I think you need to go to IAM in AWS, assign the user that's configured for dataduct to a policy which has EMR_DefaultRole, such as AmazonElasticMapReduceRole. This can be done under the permissions tab for the specified user in IAM
Currently there is no way to specify a default ARN in the config file (current documentation for creating an etl is incorrect in that regard).
Rather than update the existing documentation, I propose adding DEFAULT_TOPIC_ARN to the global config, which can be overridden in the etl pipeline itself. At least in our case, the same topic_arn is shared within the same mode.
I will add a PR to add this functionality.
The text was updated successfully, but these errors were encountered: