can't find any mention of those settings in the generated YAML, but I'll happily try to debug CDK / punchcard down to help track the issue if interested. The lambda function created still uses the default memory (128) and the default timeout (3 secs), so don't know where the issue happening. The issue in this case is that the task is timing out because of lack of memory (my stack is using around 171MB)
can't find any mention of those settings in the generated YAML, but I'll happily try to debug CDK / punchcard down to help track the issue if interested. The lambda function created still uses the default memory (128) and the default timeout (3 secs), so don't know where the issue happening. The issue in this case is that the task is timing out because of lack of memory (my stack is using around 171MB)