castleadmin
commented
3 months ago Hi @blkdot , thank you for reporting this issue.
I wasn't able to reproduce the issue on my side. I will provide some background knowledge about the inner workings. Hopefully, this will be enough to resolve the issue 🙏.
nx-serverless-cdk is just a slim glue of existing AWS tools. For the local execution of the Lambda function, AWS SAM is used. AWS SAM relies only on
- The generated Lambda function bundle (ZIP file)
- The CloudFormation template
- The
samconfig.toml
for local execution. Both can be found in the cdk.out directory after the cdk synth command has been executed.
The error you have posted seems to originate from the AWS Powertools library. This is an optional library. To exclude other error sources, I recommend throwing it out of the Lambda Source Code, generating a new cdk.out output, and testing the local execution again.
If the execution is successful, the next step would be to look into the synthesizing of the cdk.out directory. The following happens during the execution of the cdk synth command.
- The CloudFormation templates are generated according to the CDK constructs in the cdk Source Code
- The Lambda functions are built with esbuild
The NodejsFunction Construct is responsible to kick of the esbuild process. The esbuild process can be started locally (default) or in a Docker Container.
As the next test, I would recommend trying out the esbuild Docker process. If the Docker build and the local Lambda function execution succeeds then the issue is most likely related to the local UNIX setup.
To enable the Docker build, please at the following line to the default-lambda-props.ts file.
bundling: {
...
forceDockerBundling: true
},Please also check if you're using
- the latest AWS SAM version
sam --version(should be 1.121.0) - the latest node LTS version (should be v20.16.0)
- Use the same processor architecture (ARM_64, X86_64) for the Lambda function and the local execution environment (e.g. use ARM_64 on an ARM_64 laptop). This isn't required for the cloud deployment, but eases the local testing with SAM.
blkdot
{"errorType": "RangeError", "errorMessage": "Invalid time zone specified: :/etc/localtime", "trace": ["RangeError: Invalid time zone specified: :/etc/localtime", " at new DateTimeFormat ()", " at #getDateFormatter (file:///var/task/index.mjs:1101:12)", " at #generateISOTimestampWithOffset (file:///var/task/index.mjs:1119:78)", " at PowertoolsLogFormatter.formatTimestamp (file:///var/task/index.mjs:1070:50)", " at PowertoolsLogFormatter.formatAttributes (file:///var/task/index.mjs:1185:23)", " at _Logger.createAndPopulateLogItem (file:///var/task/index.mjs:1790:35)", " at _Logger.processLogItem (file:///var/task/index.mjs:1891:38)", " at _Logger.info (file:///var/task/index.mjs:1458:10)", " at Runtime.exampleHandler [as handler] (file:///var/task/index.mjs:2080:10)", " at Runtime.handleOnceNonStreaming (file:///var/runtime/index.mjs:1173:29)"]}