Deploy and operate Temporal Workers on serverless compute with help from a coding agent. The skill guides an agent through the complete AWS Lambda lifecycle: scoping, access checks, Worker implementation, packaging, deployment, Temporal registration, verification, troubleshooting, updates, and rollback.
Warning
This skill is in Public Preview and will continue to evolve. Pin the Temporal SDK, serverless Worker package, and CLI versions for long-lived projects.
Note
Temporal Serverless Workers on AWS Lambda are in Public Preview and are available to all Temporal Cloud customers without an access request. AWS Lambda is currently the only compute provider supported by this skill.
- Build Serverless Workers with the Go, Python, or TypeScript SDK.
- Package and deploy Workers to AWS Lambda with the correct architecture, timeout, and shutdown settings.
- Configure the separate AWS roles used by the Lambda function and by Temporal.
- Register a Worker Deployment Version, validate its Task Queue binding, and set it current.
- Verify a deployment from both Temporal Workflow history and Lambda logs.
- Diagnose Workers that are not invoked or do not complete Tasks.
- Publish immutable Lambda versions, update deployments, and roll back safely.
- Add OpenTelemetry observability with the AWS Distro for OpenTelemetry.
- Configure self-hosted Temporal deployments that meet the serverless prerequisites.
| Area | Supported |
|---|---|
| Compute | AWS Lambda — Public Preview |
| Temporal | Temporal Cloud and self-hosted Temporal Service |
| SDKs | Go, Python, TypeScript |
| Other compute providers | Not currently supported |
For Temporal Cloud, the Namespace must be hosted on AWS. The Namespace and Lambda function may be in different AWS regions.
Before starting, make sure you can sign in to:
- An AWS account with permission to inspect and create the required Lambda, IAM, CloudFormation, and logging resources.
- A Temporal Cloud Namespace hosted on AWS, or a compatible self-hosted Temporal Service.
You do not need to install or configure the AWS CLI, tcld, or the Temporal CLI before you begin. The skill checks what is already available and can help set up the tools and supported login flows needed for the task. If you prefer not to install a CLI, or a login method is unavailable, it can guide you through the corresponding Temporal Cloud UI or AWS console steps instead. It never asks you to paste credentials or secrets into the conversation.
Clone the repository into your coding agent's skills directory.
mkdir -p ~/.codex/skills
git clone https://github.com/temporalio/skill-temporal-serverless.git \
~/.codex/skills/temporal-serverlessIf CODEX_HOME is set, install the repository under $CODEX_HOME/skills/temporal-serverless instead.
mkdir -p ~/.claude/skills
git clone https://github.com/temporalio/skill-temporal-serverless.git \
~/.claude/skills/temporal-serverlessFor another coding agent that supports skills, use its documented skills directory and keep SKILL.md at the root of the installed folder. Restart or open a new agent session after installation if the skill is not discovered immediately.
To update a Git-based installation:
git -C /path/to/temporal-serverless pull --ff-onlyAsk your coding agent for the outcome you want. For example:
Deploy a Python Temporal Serverless Worker to AWS Lambda.
My Serverless Worker is not being invoked. Diagnose it without changing resources.
Publish an immutable build of this TypeScript Worker and roll the deployment forward.
Add OpenTelemetry tracing to my Go Serverless Worker on Lambda.
For a new deployment, the skill follows five stages:
- Scope — confirm the SDK, compute provider, Namespace, region, and resource-naming prefix.
- Access — verify AWS and Temporal identities and permissions, then present the exact billable resources for approval.
- Build — install the serverless Worker package, inspect its current API, author the Worker, and deploy it.
- Connect — configure Temporal's invocation role, register the Worker Deployment Version, validate the Task Queue binding, and set the version current.
- Verify and hand back — run a Workflow, confirm two independent health signals, inventory every created resource, and offer teardown.
Nothing is created before you approve the resource list. Troubleshooting and inspection requests skip the deployment walkthrough and begin with read-only diagnostics.
- Serverless Workers and their APIs are Public Preview, not generally available.
- Every Workflow must use a Worker Versioning behavior:
PinnedorAutoUpgrade. - The deployment name and build ID in Worker code must exactly match the registered Worker Deployment Version.
- Production releases should map each build ID to one immutable Lambda version.
- Activities must finish within the Lambda invocation limit and configured shutdown buffer; Workflow duration remains unbounded.
- Secrets belong in a secret store for shared or production deployments, not plaintext environment variables.
- Temporal creates and manages the Worker Controller Instance (WCI); this skill never creates or manages it directly.
| Path | Contents |
|---|---|
SKILL.md |
Core workflow, safety gates, provider rules, and reference routing |
references/concepts.md |
Architecture, invocation flow, autoscaling, lifecycle, constraints, and use cases |
references/sdk-configuration.md |
Go, Python, and TypeScript packages, entry points, versioning behavior, and tuned defaults |
references/aws-lambda/setup.md |
End-to-end deployment, verification, and teardown workflow |
references/aws-lambda/iam.md |
Operator permissions, Lambda execution role, and Temporal invocation role |
references/aws-lambda/diagnostics.md |
Diagnostic decision tree and WCI inspection |
references/aws-lambda/versioning.md |
Immutable releases, updates, and rollback |
references/aws-lambda/observability.md |
OpenTelemetry and ADOT configuration |
references/aws-lambda/self-hosted.md |
Self-hosted Temporal prerequisites and configuration |
assets/ |
CloudFormation templates for Temporal invocation roles |
Feedback is welcome in the Temporal Community Slack, in the #topic-ai channel, or through GitHub issues.