This message was deleted.

fixed this problem by granting IAM permissions in aws-auth to the account associated with cloud credentials