I encountered the same issue and it was because the case of the function name was off in the resources section. I renamed the lambda function name in the resources section to match the lambda function name exactly from .serverless/cloudformation-template-update-stack.json and the S3Key error went away.