aws-samples / aws-samples/cloudformation-studio-domain
CloudFormation did not receive a response from your Custom Resource. Please check your logs for requestId [2cceedaf-dbdb-4ed9-95ba-10cb948ce3ea]. If you are using the Python cfn-response module, you may need to update your Lambda function code so that CloudFormation can attach the updated version.
- Dominant language
- No language data
- Stars
- 14
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
After fixing some issues with the incorrectly named Lambda zip you need to upload (should be "cfnResponse_layer.zip") and an empty result for `${AWS::Partition}` for me in the Frankfurt region (if you are not in a government cloud, just hardcode "aws"), I am running into this issue:
```
CloudFormation did not receive a response from your Custom Resource. Please check your logs for requestId [1111111-aaaaaaa-222222222-bbbbbbbbb]. If you are using the Python cfn-response module, you may need to update your Lambda function code so that CloudFormation can attach the updated version.
```
I am not sure what I can do here... the `domain_function` Lambda layer simply imports `cfnresponse`, nowhere is there a package version specified. Also, all the Lambdas are already configured for Python 3.8, which doesn't seem too old as per time of writing.
I googled around and found [this page](https://aws.amazon.com/premiumsupport/knowledge-center/cloudformation-cfn-response-lambda/). Does this mean that there is a Lambda somewhere in my account that already defines a cfn-response but is outdated?
Contributor guide
Assessment
This issue has not been assessed yet.