Masashi Tomooka

By the way, for anyone who wants to use AppSync Events without Amplify libraries, the integ test code in CDK below helped a lot. You need to handle sigv4 by...

related: https://github.com/aws/aws-cdk/issues/34494

It does not seem to support Arm environment yet. > 10:26:32 AM | UPDATE_FAILED | AWS::CodeBuild::Project | ContainerImageBuil...47a30amd64C13E3549 Failed to call UpdateProject, reason: Unsupported DockerServer environment type: ARM_CONTAINER (Service: AWSCodeBuild;...

We must not execute `docker buildx create --use` because it overrides the required configuration for CodeBuild docker server. (resolved with https://github.com/tmokmss/deploy-time-build/issues/49) https://github.com/tmokmss/deploy-time-build/blob/c97f9dd0485019eb1fbc38eaed4a28ce63172aa3/src/container-image-build.ts#L108

Current workaround using escape hatch: ```ts // Use ContainerImageBuild to inject deploy-time values in the build environment const image = new ContainerImageBuild(this, 'Build', { directory: join('..', 'app'), platform: Platform.LINUX_AMD64, });...

It will require some manual work to migrate a function to ESM if a customer is using cfn-response module as described in [this doc](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cfn-lambda-function-code-cfnresponsemodule.html). I'm not strongly against defaulting ESM...

Looking forward to support of `@aws-amplify/adapter-nextjs` as well :) ``` npm error While resolving: [email protected] npm error Found: [email protected] npm error node_modules/next npm error next@"16.0.1" from the root project npm...

Nevermind. I misunderstood that AWS_LAMBDA_EXEC_WRAPPER is a path to binary but it turns out that it is just a shell script ([lwa](https://github.com/awslabs/aws-lambda-web-adapter/blob/main/layer/bootstrap), [otel, nodejs](https://github.com/aws-observability/aws-otel-lambda/blob/main/nodejs/scripts/otel-handler)). I merged the two scripts and...

Hi @bnusunny I'm currently trying this configuration on Lambda Node.js runtime, but now realized that things are not such simple. So Lambda + otel seems to rely on [`AwsLambdaInstrumentation` module...

@bnusunny That's awesome, thanks! I think I tried the approach but it somehow didn't work; it appeared the span context was not propagated? still investigating though. I might have mesed...