- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
I encountered this issue even when FunctionCode and FunctionConfig present. It turns out to be an existing Function created at the previous CloudFormation deployment, when updating via Change Sets, it may cause this error.
Without further error messages, my educated guess is that the internal comparison of the change set returns an empty diff.
Changing the Name is our current workaround.
beantwortet vor 3 Jahren
Add FunctionConfig property to resolve the error. I had to add this property even though the documentation says it's optional.
beantwortet vor 5 Jahren
I'm seeing the same thing. What do you have for your FunctionCode block? I have tried fileb://filename.js and filename.js and the yaml multi line like FunctionCode: | (lines of javascript) with the same results.
Edited by: acaird on Sep 1, 2021 8:39 AM
beantwortet vor 5 Jahren
In my case, I got that error message because I already had another cloudfront function with the same name that I was trying to create.
beantwortet vor 3 Jahren

Omg, thank you! This saved my bacon today.