- Más nuevo
- Más votos
- Más comentarios
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.
respondido hace 4 años
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
respondido hace 4 años
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.
respondido hace 7 meses
Contenido relevante
preguntada hace 8 meses
preguntada hace 7 meses
preguntada hace un año
preguntada hace 8 meses

Hi, did you ever find a solution for this?