[BUG]The default value of enableLambdaSnapStart in cdk.json is "True".

[moritalous]

🐞Bug description

The following is written in the Optional Parameters section of the README.

• --enable-lambda-snapstart: Enable Lambda SnapStart (default: disabled). If this flag is set, improves cold start times for Lambda functions, providing faster response times for better user experience.

However, the value of enableLambdaSnapStart in cdk.json is true, so I think the default should be true or the value in cdk.json is incorrect.

Snap start is enabled if you deploy with npx cdk deploy instead of ./bin.sh.

[statefb]

Thank you for pointing this out! This apparent contradiction is intentional:

For ./bin.sh deployments: SnapStart is disabled by default as this is our entry point for first-time users across all regions, prioritizing compatibility over performance

For direct CDK deployments: SnapStart is enabled by default in cdk.json as we assume CDK users are advanced users who would benefit from the performance improvements

This design balances accessibility for newcomers while providing optimal performance for advanced users, considering regional limitations and costs of Python Lambda SnapStart.