- Newest
- Most votes
- Most comments
YMMV, but the problem for me was that the "aws:SourceArn" condition on my role's trust policy was set to the wrong ARN. Setting it to the ARN of the resource that needed to assume the role fixed it.
Did the role you create have the required policy as described in the following links?
These might also help: https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Authorizing.IAM.CreateRole.html https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Authorizing.IAM.AddRoleToDBCluster.html
In case anyone else runs across this, if you're using IaC, I found this can also be caused by attempting to associate the role before the permissions are attached. In Terraform, this was fixed by adding a depends_on meta-argument to the resource/role association.
Relevant content
- asked 2 years ago
- AWS OFFICIALUpdated 2 years ago

Hi, did you ever find a solution for this?