I had the exact same situation you are describing however without having more information the root cause of your precise problem is not easy to identify.

What I would suggest is to double check the IAM policy attached to the role you are using and verify that you are using the RDS instance "Resource ID" and not the "Instance id".