2 Answers
- Newest
- Most votes
- Most comments
0
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
answered 2 years ago
0
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.
answered 2 years ago
Relevant content
- asked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 2 years ago
Hi, did you ever find a solution for this?