Update for released TS

Sushisource · Sushisource · commit c8f9b463a26d · 2026-04-30T17:32:34.000-07:00
diff --git a/.gitignore b/.gitignore
@@ -114,3 +114,4 @@ package-lock.json
 
 **/client.key
 **/client.pem
+worker-versioning/.claude/settings.local.json
diff --git a/.scripts/list-of-samples.json b/.scripts/list-of-samples.json
@@ -25,7 +25,6 @@
     "hello-world-mtls",
     "interceptors-opentelemetry",
     "lambda-worker",
-    "message-passing",
     "monorepo-folders",
     "mutex",
     "nestjs-exchange-rates",
@@ -56,4 +55,4 @@
     "message-passing/safe-message-handlers",
     "polling/infrequent"
   ]
-}
+}
diff --git a/lambda-worker/README.md b/lambda-worker/README.md
@@ -13,10 +13,6 @@ which `@temporalio/lambda-worker` automatically detects and uses to produce stru
 logs that CloudWatch Logs can parse natively. If you don't need structured logging, you can
 remove the dependency and the SDK will fall back to its default human-readable logger.
 
-> **Note:** `@temporalio/lambda-worker` is not yet published. The `package.json` currently
-> references it via a local `file:` path to `../../sdk-node/packages/lambda-worker`.
-> TODO: Replace with a versioned dependency (e.g. `^1.15.0`) once the package is published.
-
 ## Prerequisites
 
 - A [Temporal Cloud](https://temporal.io/cloud) namespace (or a self-hosted Temporal
@@ -29,29 +25,46 @@ remove the dependency and the SDK will fall back to its default human-readable l
 
 ## Files
 
-| File                                            | Description                                                                                                  |
-| ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------ |
+| File                                            | Description                                                                                                       |
+| ----------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
 | `src/index.ts`                                  | Lambda entry point — configures the worker, registers Workflows/Activities, enables OTel, and exports the handler |
-| `src/workflows.ts`                              | Sample Workflow that executes a greeting Activity                                                             |
-| `src/activities.ts`                             | Sample Activity that returns a greeting string                                                                |
-| `src/client.ts`                                 | Helper program to start a Workflow execution from a local machine                                             |
-| `src/scripts/build-workflow-bundle.ts`          | Pre-bundles Workflow code with OTel interceptor modules for Lambda cold start performance                     |
-| `temporal.toml`                                 | Temporal client connection configuration (update with your namespace)                                         |
-| `otel-collector-config.yaml`                    | OpenTelemetry Collector configuration for ADOT (routes metrics to CloudWatch, traces to X-Ray)                |
-| `deploy-lambda.sh`                              | Packages and deploys the Lambda function                                                                      |
-| `mk-iam-role.sh`                                | Creates the IAM role that allows Temporal Cloud to invoke the Lambda                                          |
-| `iam-role-for-temporal-lambda-invoke-test.yaml` | CloudFormation template for the IAM role                                                                      |
-| `extra-setup-steps`                             | Additional IAM and Lambda configuration for OpenTelemetry support                                             |
+| `src/workflows.ts`                              | Sample Workflow that executes a greeting Activity                                                                 |
+| `src/activities.ts`                             | Sample Activity that returns a greeting string                                                                    |
+| `src/client.ts`                                 | Helper program to start a Workflow execution from a local machine                                                 |
+| `src/scripts/build-workflow-bundle.ts`          | Pre-bundles Workflow code with OTel interceptor modules for Lambda cold start performance                         |
+| `temporal.toml`                                 | Temporal client connection configuration (update with your namespace)                                             |
+| `otel-collector-config.yaml`                    | OpenTelemetry Collector configuration for ADOT (routes metrics to CloudWatch, traces to X-Ray)                    |
+| `deploy-lambda.sh`                              | Packages and deploys the Lambda function                                                                          |
+| `mk-iam-role.sh`                                | Creates the IAM role that allows Temporal Cloud to invoke the Lambda                                              |
+| `iam-role-for-temporal-lambda-invoke-test.yaml` | CloudFormation template for the IAM role                                                                          |
+| `extra-setup-steps`                             | Additional IAM and Lambda configuration for OpenTelemetry support                                                 |
 
 ## Setup
 
-### 1. Configure Temporal connection
+The instructions here are a slimmed down version of the more complete getting started guide which
+you can find [here](https://docs.temporal.io/production-deployment/worker-deployments/serverless-workers/aws-lambda).
+
+### 1. Create a lambda function for your TypeScript worker
+
+Use either the AWS web UI or CLI to create a Node.js runtime Lambda function. Ex:
+
+```bash
+aws lambda create-function \
+  --function-name my-temporal-worker \
+  --runtime nodejs22.x \
+  --handler lib/index.handler \
+  --role arn:aws:iam::<YOUR_ACCOUNT_ID>:role/my-temporal-worker-execution \
+  --timeout 600 \
+  --memory-size 256
+```
+
+### 2. Configure Temporal connection
 
 Edit `temporal.toml` with your Temporal Cloud namespace address and credentials. In production,
 we'd recommend reading your credentials from a secret store, but to keep this example simple
 the toml file defaults to reading them from keys bundled along with the Lambda code.
 
-### 2. Create the IAM role
+### 3. Create the IAM role
 
 This creates the IAM role that Temporal Cloud assumes to invoke your Lambda function:
 
@@ -62,57 +75,24 @@ This creates the IAM role that Temporal Cloud assumes to invoke your Lambda func
 The External ID is provided by Temporal Cloud in your namespace's serverless worker
 configuration.
 
-### 3. (Optional) Enable OpenTelemetry
-
-The sample calls `applyDefaults(config)` in the handler, which registers Temporal SDK
-interceptors for tracing Workflow, Activity, and Nexus calls, and configures the Core SDK
-to export metrics via OTLP. To complete the setup, attach two ADOT Lambda layers:
-
-1. **ADOT JavaScript layer** — auto-instruments the handler and exports Node.js-side
-   traces to X-Ray. See [this page](https://aws-otel.github.io/docs/getting-started/lambda/lambda-js)
-   for the layer ARN for your region.
-2. **ADOT Collector layer** (`aws-otel-collector-amd64`) — runs the OTel Collector as a
-   Lambda extension, receiving Temporal Core SDK metrics via OTLP and forwarding them to
-   CloudWatch/X-Ray. See [this page](https://aws-otel.github.io/docs/getting-started/lambda)
-   for the layer ARN.
-
-Update `otel-collector-config.yaml` with your function name and region, then set the
-following environment variables on your Lambda:
-
-```
-AWS_LAMBDA_EXEC_WRAPPER=/opt/otel-instrument
-OPENTELEMETRY_COLLECTOR_CONFIG_URI=/var/task/otel-collector-config.yaml
-```
-
-`AWS_LAMBDA_EXEC_WRAPPER` enables the JS layer's auto-instrumentation.
-`OPENTELEMETRY_COLLECTOR_CONFIG_URI` points the collector at the custom config that
-routes metrics to CloudWatch EMF and traces to X-Ray.
+### 4. (Optional) Enable OpenTelemetry
 
-Enable X-Ray active tracing on the Lambda function (required for traces to appear):
-
-```bash
-aws lambda update-function-configuration --function-name <function-name> \
-  --tracing-config Mode=Active
-```
+If you want traces, metrics, and logs, you'll have to attach the ADOT layer to your Lambda function.
+You will need to add the appropriate layer for your runtime and region. See [this page
+](https://aws-otel.github.io/docs/getting-started/lambda#getting-started-with-aws-lambda-layers)
+for more info. See also the [Temporal docs on adding observability
+](https://docs.temporal.io/develop/typescript/workers/serverless-workers/aws-lambda#add-observability)
+for additional TypeScript-specific configuration.
 
 Then run the extra setup to grant the Lambda role the necessary permissions:
 
 ```bash
 ./extra-setup-steps <role-name> <function-name> <region> <account-id>
 ```
 
-### 4. Deploy the Lambda function
+Update `otel-collector-config.yaml` with your function name and region as needed.
 
-Create a Lambda function in AWS with:
-
-- **Runtime**: Node.js >=20
-- **Handler**: `index.handler` (the default)
-- **Architecture**: x86_64
-
-It's likely you will need to increase the default memory limit in AWS for your lambda. A minimum of
-256MB is recommended.
-
-Then deploy:
+### 5. Deploy the Lambda function
 
 ```bash
 ./deploy-lambda.sh <function-name>
@@ -121,7 +101,11 @@ Then deploy:
 This compiles TypeScript, pre-bundles Workflow code, packages everything with dependencies,
 and uploads to AWS Lambda.
 
-### 5. Start a Workflow
+### 6. Configure Temporal to be able to invoke your lambda function
+
+Refer to the docs [here](https://docs.temporal.io/production-deployment/worker-deployments/serverless-workers/aws-lambda#create-worker-deployment-version).
+
+### 7. Start a Workflow
 
 Use the starter program to execute a Workflow on the Lambda worker, using
 the same config file the Lambda uses for connecting to the server:
diff --git a/lambda-worker/deploy-lambda.sh b/lambda-worker/deploy-lambda.sh
@@ -3,7 +3,6 @@ set -euo pipefail
 
 FUNCTION_NAME="${1:?Usage: deploy-lambda.sh <function-name>}"
 SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
-SDK_DIR="$SCRIPT_DIR/../../sdk-node"
 
 # Build TypeScript
 cd "$SCRIPT_DIR"
@@ -22,22 +21,15 @@ cp "$SCRIPT_DIR/lib/"*.js "$SCRIPT_DIR/package/"
 # Copy workflow bundle alongside the handler
 cp "$SCRIPT_DIR/workflow-bundle.js" "$SCRIPT_DIR/package/"
 
-# Install production dependencies.
-# TODO: Once @temporalio/lambda-worker is published, remove the sed and the
-# manual copy below — npm install will handle everything.
+# Install production dependencies
 cd "$SCRIPT_DIR/package"
-sed '/@temporalio\/lambda-worker/d' "$SCRIPT_DIR/package.json" > package.json
+cp "$SCRIPT_DIR/package.json" package.json
 npm install --omit=dev --ignore-scripts
 
 # Strip native binaries for platforms other than Lambda's (linux x86_64)
 find node_modules/@temporalio/core-bridge/releases -mindepth 1 -maxdepth 1 \
     ! -name 'x86_64-unknown-linux-gnu' -exec rm -rf {} +
 
-# Manually place the local lambda-worker package (not yet published)
-mkdir -p node_modules/@temporalio/lambda-worker
-cp "$SDK_DIR/packages/lambda-worker/package.json" node_modules/@temporalio/lambda-worker/
-cp -r "$SDK_DIR/packages/lambda-worker/lib" node_modules/@temporalio/lambda-worker/
-
 # Copy config files and certs
 cp "$SCRIPT_DIR/temporal.toml" "$SCRIPT_DIR/otel-collector-config.yaml" \
    "$SCRIPT_DIR/client.pem" "$SCRIPT_DIR/client.key" "$SCRIPT_DIR/package/"
diff --git a/lambda-worker/extra-setup-steps.sh b/lambda-worker/extra-setup-steps.sh
diff --git a/lambda-worker/iam-role-for-temporal-lambda-invoke-test.yaml b/lambda-worker/iam-role-for-temporal-lambda-invoke-test.yaml
@@ -1,6 +1,6 @@
 # CloudFormation template for creating an IAM role that Temporal Cloud can assume to invoke Lambda functions.
 AWSTemplateFormatVersion: '2010-09-09'
-Description: Creates an IAM role that Temporal Cloud can assume to invoke Lambda functions for Serverless Workers.
+Description: Creates an IAM role that Temporal Cloud can assume to invoke multiple Lambda functions for Serverless Workers.
 
 Parameters:
   AssumeRoleExternalId:
@@ -10,11 +10,15 @@ Parameters:
     MinLength: 5
     MaxLength: 45
 
-  LambdaFunctionARN:
-    Type: String
+  LambdaFunctionARNs:
+    Type: CommaDelimitedList
     Description: >-
-      The ARN of the Lambda function to invoke
-      (e.g., arn:aws:lambda:us-west-2:123456789012:function:worker-1)
+      Comma-separated list of Lambda function ARNs to invoke (e.g.,
+      arn:aws:lambda:us-west-2:123456789012:function:worker-1,arn:aws:lambda:us-west-2:123456789012:function:worker-2)
+
+  RoleName:
+    Type: String
+    Default: 'Temporal-Cloud-Serverless-Worker'
 
 Metadata:
   AWS::CloudFormation::Interface:
@@ -26,26 +30,34 @@ Metadata:
       - Label:
           default: 'Lambda Configuration'
         Parameters:
-          - LambdaFunctionARN
+          - LambdaFunctionARNs
+          - RoleName
     ParameterLabels:
       AssumeRoleExternalId:
         default: 'External ID (provided by Temporal Cloud)'
-      LambdaFunctionARN:
-        default: 'Lambda Function ARN'
+      LambdaFunctionARNs:
+        default: 'Lambda Function ARNs (comma-separated list)'
+      RoleName:
+        default: 'IAM Role Name'
 
 Resources:
   TemporalCloudServerlessWorker:
     Type: AWS::IAM::Role
     Properties:
-      RoleName: !Sub
-        - 'Temporal-Cloud-Serverless-Worker-${LambdaName}'
-        - LambdaName: !Select [6, !Split [':', !Ref LambdaFunctionARN]]
+      RoleName: !Sub '${RoleName}-${AWS::StackName}'
       AssumeRolePolicyDocument:
         Version: '2012-10-17'
         Statement:
           - Effect: Allow
             Principal:
-              AWS: [arn:aws:iam::031568301006:role/wci-lambda-invoke]
+              AWS:
+                [
+                  arn:aws:iam::902542641901:role/wci-lambda-invoke,
+                  arn:aws:iam::160190466495:role/wci-lambda-invoke,
+                  arn:aws:iam::819232936619:role/wci-lambda-invoke,
+                  arn:aws:iam::829909441867:role/wci-lambda-invoke,
+                  arn:aws:iam::354116250941:role/wci-lambda-invoke,
+                ]
             Action: sts:AssumeRole
             Condition:
               StringEquals:
@@ -65,9 +77,9 @@ Resources:
             Action:
               - lambda:InvokeFunction
               - lambda:GetFunction
-            Resource: [!Ref LambdaFunctionARN]
+            Resource: !Ref LambdaFunctionARNs
       Roles:
-        - !Ref TemporalCloudServerlessWorker
+        - !Sub '${RoleName}-${AWS::StackName}'
 
 Outputs:
   RoleARN:
@@ -78,8 +90,8 @@ Outputs:
 
   RoleName:
     Description: The name of the IAM role
-    Value: !Ref TemporalCloudServerlessWorker
+    Value: !Ref RoleName
 
-  LambdaFunctionARN:
-    Description: The Lambda function ARN that can be invoked
-    Value: !Ref LambdaFunctionARN
+  LambdaFunctionARNs:
+    Description: The Lambda function ARNs that can be invoked
+    Value: !Join [', ', !Ref LambdaFunctionARNs]
diff --git a/lambda-worker/mk-iam-role.sh b/lambda-worker/mk-iam-role.sh
@@ -13,5 +13,5 @@ aws cloudformation create-stack \
   --template-body file://iam-role-for-temporal-lambda-invoke-test.yaml \
   --parameters \
     ParameterKey=AssumeRoleExternalId,ParameterValue="$EXTERNAL_ID" \
-    ParameterKey=LambdaFunctionARN,ParameterValue="$LAMBDA_ARN" \
+    ParameterKey=LambdaFunctionARNs,ParameterValue="$LAMBDA_ARN" \
   --capabilities CAPABILITY_NAMED_IAM
diff --git a/lambda-worker/otel-collector-config.yaml b/lambda-worker/otel-collector-config.yaml
@@ -15,8 +15,7 @@ exporters:
     # AWS EMF exporter for metrics
     # These are example configurations
     namespace: TemporalWorkerMetrics
-    # log_group_name: /aws/lambda/<your-function-name>
-    log_group_name: /aws/lambda/sdk-worker-typescript
+    log_group_name: /aws/lambda/<your-function-name>
     region: us-west-2
     dimension_rollup_option: NoDimensionRollup
     resource_to_telemetry_conversion:
@@ -32,7 +31,7 @@ service:
       exporters: [awsemf]
   telemetry:
     logs:
-      level: debug
+      level: info
     metrics:
       address: localhost:8888
 # @@@SNIPEND
diff --git a/lambda-worker/package.json b/lambda-worker/package.json
@@ -12,14 +12,14 @@
     "workflow": "ts-node src/client.ts"
   },
   "dependencies": {
-    "@temporalio/activity": "^1.15.0",
-    "@temporalio/client": "^1.15.0",
-    "@temporalio/envconfig": "^1.15.0",
-    "@temporalio/lambda-worker": "file:../../sdk-node/packages/lambda-worker",
-    "@temporalio/worker": "^1.15.0",
-    "@temporalio/workflow": "^1.15.0",
+    "@temporalio/activity": "^1.17.0",
+    "@temporalio/client": "^1.17.0",
+    "@temporalio/envconfig": "^1.17.0",
+    "@temporalio/lambda-worker": "^1.17.0",
+    "@temporalio/worker": "^1.17.0",
+    "@temporalio/workflow": "^1.17.0",
     "@aws-lambda-powertools/logger": "^2.0.0",
-    "@temporalio/interceptors-opentelemetry": "^1.15.0",
+    "@temporalio/interceptors-opentelemetry": "^1.17.0",
     "@opentelemetry/exporter-trace-otlp-grpc": "^0.52.0",
     "@opentelemetry/resources": "^1.25.1",
     "@opentelemetry/sdk-trace-base": "^1.25.1",
diff --git a/lambda-worker/sample.temporal.toml b/lambda-worker/sample.temporal.toml
diff --git a/lambda-worker/temporal.toml b/lambda-worker/temporal.toml
@@ -1,6 +1,6 @@
 [profile.default]
-address = "ns-sdk-dev-01.temporal-dev.tmprl-test.cloud:7233"
-namespace = "ns-sdk-dev-01.temporal-dev"
+address = "<your-namespace>.<account>.tmprl.cloud:7233"
+namespace = "<your-namespace>.<account>"
 [profile.default.tls]
 client_cert_path = "client.pem"
 client_key_path = "client.key"
diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml

Original file line number	Diff line number	Diff line change
`@@ -114,3 +114,4 @@ package-lock.json`
`114`	`114`
`115`	`115`	`**/client.key`
`116`	`116`	`**/client.pem`
	`117`	`+worker-versioning/.claude/settings.local.json`