That’s usually caused by an IAM issue, not a code issue. Did something change with your IAM roles?
If you look at the configuration for your Lambda functions, you’ll see the role that they’re trying to assume - is it correct? Does it have a trust relationship with the Lambda service (i.e. lambda.amazonaws.com)?