I've been investigating this, and I believe the lambda issue is actually due to the way CDK works, rather than an issue with localstack.
When you create a lambda through CDK, it uses the CDK bucket to upload the code (this bucket is created when you run "cdk bootstrap").
The parameters are in fact missing because CDK would normally pass them when deploying (e.g. the parameter for bucket would point to the cdk staging bucket in S3).
Hi Matt,
I've been investigating this, and I believe the lambda issue is actually due to the way CDK works, rather than an issue with localstack.
When you create a lambda through CDK, it uses the CDK bucket to upload the code (this bucket is created when you run "cdk bootstrap").
The parameters are in fact missing because CDK would normally pass them when deploying (e.g. the parameter for bucket would point to the cdk staging bucket in S3).
See the following for passing parameters when calling cloudformation:
aws.amazon.com/blogs/devops/passin...
We should be able to get this working if we manually upload the code (as CDK would do), then set the parameters to match.