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
The first replication is created and programmatically in the process spawns a service-linked IAM role apparently called "AWSServiceRoleForDMSServerless". Subsequent deploying configs try to do the exact same thing, spawning a role named "AWSServiceRoleForDMSServerless" which fails because the role with that name already exists. This means only the first replication config is provisioned and all others fail.
Given that the module does not support custom roles or role suffixes, I cannot see any workaround for this behavior.
Relevant Error/Panic Output Snippet
Error: creating DMS Replication Config (dev-babel-cdc-lo-batch): InvalidParameterValueException: Caught exception while trying to create the service-linked IAM role for DMS Serverless. Please ensure the account user has permission to create service-linked roles. Please follow the steps for using SLR here: https://docs.aws.amazon.com/IAM/latest/UserGuide/using-service-linked-roles.html"errorCode": "InvalidInputException","errorMessage": "Service role name AWSServiceRoleForDMSServerless has been taken in this account, please try a different suffix."
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
Volunteering to Work on This Issue
If you are interested in working on this issue, please leave a comment.
If this would be your first contribution, please review the contribution guide.
Terraform Core Version
1.4.6
AWS Provider Version
5.49.0
Affected Resource(s)
aws_dms_replication_config
Expected Behavior
Create multiple replication configs
Actual Behavior
The first replication is created and programmatically in the process spawns a service-linked IAM role apparently called "AWSServiceRoleForDMSServerless". Subsequent deploying configs try to do the exact same thing, spawning a role named "AWSServiceRoleForDMSServerless" which fails because the role with that name already exists. This means only the first replication config is provisioned and all others fail.
Given that the module does not support custom roles or role suffixes, I cannot see any workaround for this behavior.
Relevant Error/Panic Output Snippet
Terraform Configuration Files
Steps to Reproduce
Try to provision multiple replication configs. Watch them fail with the service-linked role error. Confirm reason for SLR failure in CloudTrail.
Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
DMS docs
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: