docs: self-hosted setup for serverless workers#4476
Open
lennessyy wants to merge 11 commits intofeat/serverless-worker-prereleasefrom
Open
docs: self-hosted setup for serverless workers#4476lennessyy wants to merge 11 commits intofeat/serverless-worker-prereleasefrom
lennessyy wants to merge 11 commits intofeat/serverless-worker-prereleasefrom
Conversation
Covers enabling the Worker Controller via dynamic config, configuring AWS credentials for the Temporal server, and creating the Lambda invocation role with a CloudFormation template adapted for self-hosted. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
📖 Docs PR preview links |
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Add how to view WCI workflows using TemporalNamespaceDivision filter to both the self-hosted setup page and the deploy guide. Add aws sts get-caller-identity tip for finding the server's IAM ARN. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
lennessyy
commented
Apr 23, 2026
|
|
||
| ## Enable the Worker Controller {#enable-worker-controller} | ||
|
|
||
| The Worker Controller is the server component that monitors Task Queues and invokes compute providers. |
Contributor
Author
There was a problem hiding this comment.
Suggested change
| The Worker Controller is the server component that monitors Task Queues and invokes compute providers. | |
| The Worker Controller Instance (WCI) is the server component that monitors Task Queues and invokes compute providers. |
|
|
||
| The Temporal Service watches the dynamic config file for changes and applies updates without a restart. | ||
|
|
||
| ### Worker Controller dynamic config reference {#dynamic-config-reference} |
Contributor
Author
There was a problem hiding this comment.
This needs to go to dynamic config page, not here.
| - Self-hosted | ||
| --- | ||
|
|
||
| Temporal Cloud handles Serverless Worker infrastructure automatically. |
Contributor
Author
There was a problem hiding this comment.
We don't need this first paragraph.
|
|
||
| Use this role ARN when creating the Worker Deployment Version. | ||
|
|
||
| ## Verify the Worker Controller {#verify-worker-controller} |
Contributor
Author
There was a problem hiding this comment.
On second thought I think we don't need this section. Just a ## Next steps section that links to AWS Lambda deploy guide is enough,
- Remove first paragraph (Cloud comparison) - Add brief overview of the three setup steps - Use "Worker Controller Instance (WCI)" instead of "Worker Controller" - Move dynamic config reference table out (belongs on dynamic config page) - Replace verify section with Next steps linking to deploy guide Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
02strich
reviewed
Apr 24, 2026
| - A Temporal Cloud account or a self-hosted Temporal Service vx.xx.x or later. | ||
| - Your Temporal Service frontend must be reachable from the Lambda execution environment. For Temporal Cloud, no additional configuration is needed. For self-hosted deployments on a private network, configure the Lambda function with [VPC access](https://docs.aws.amazon.com/lambda/latest/dg/configuration-vpc.html) to reach the Temporal frontend. | ||
| - For self-hosted deployments, complete the [self-hosted setup](/production-deployment/worker-deployments/serverless-workers/self-hosted-setup) before following this guide. | ||
| - The Temporal Service frontend must be reachable from the Lambda execution environment. For Temporal Cloud, no additional configuration is needed. For self-hosted deployments on a private network, configure the Lambda function with [VPC access](https://docs.aws.amazon.com/lambda/latest/dg/configuration-vpc.html) to reach the Temporal frontend. |
There was a problem hiding this comment.
Suggested change
| - The Temporal Service frontend must be reachable from the Lambda execution environment. For Temporal Cloud, no additional configuration is needed. For self-hosted deployments on a private network, configure the Lambda function with [VPC access](https://docs.aws.amazon.com/lambda/latest/dg/configuration-vpc.html) to reach the Temporal frontend. | |
| - The Temporal Service frontend must be reachable from the Lambda execution environment. For Temporal Cloud, no additional configuration is needed. For self-hosted deployments on a private network, use features like [VPC access](https://docs.aws.amazon.com/lambda/latest/dg/configuration-vpc.html) to reach the Temporal frontend. |
| This page covers the prerequisites for running [Serverless Workers](/serverless-workers) on a self-hosted Temporal | ||
| Service with AWS Lambda: | ||
|
|
||
| 1. Enable the Worker Controller Instance (WCI) on the server through dynamic configuration. |
There was a problem hiding this comment.
Suggested change
| 1. Enable the Worker Controller Instance (WCI) on the server through dynamic configuration. | |
| 1. Enable the Worker Controller on the server through dynamic configuration. |
|
|
||
| ## Enable the Worker Controller {#enable-worker-controller} | ||
|
|
||
| The Worker Controller Instance (WCI) is the server component that monitors Task Queues and invokes compute providers. It |
There was a problem hiding this comment.
Suggested change
| The Worker Controller Instance (WCI) is the server component that monitors Task Queues and invokes compute providers. It | |
| The Worker Controller is the server component that monitors Task Queues and invokes compute providers. It |
Contributor
Author
There was a problem hiding this comment.
My concern with this is that users will confuse this with https://github.com/temporalio/temporal-worker-controller
These are not the same thing right😅? At least per my understanding these are very different things. But we've already named the Kubernetes thing Worker Controller. Even though this is an internal component, it's a nice one to explain to users so they can understand how it works. It would be great if we can avoid a complete name collision
There was a problem hiding this comment.
yeah, our naming in this department has been sub-optimal. Let's leave it as WCI - but make sure that it is always WCI and never worker controller?!
Co-authored-by: Stefan Richter <stefan@02strich.de>
02strich
reviewed
Apr 25, 2026
| - no-sync | ||
| ``` | ||
|
|
||
| To enable the Worker Controller for specific Namespaces instead of globally: |
There was a problem hiding this comment.
Suggested change
| To enable the Worker Controller for specific Namespaces instead of globally: | |
| To enable the Worker Controller Instance (WCI) for specific Namespaces instead of globally: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
TemporalIamRoleArnparameter instead of hardcoded Temporal Cloud accounts)Test plan
temporal-auto-scaled-workers🤖 Generated with Claude Code
┆Attachments: EDU-6254 docs: self-hosted setup for serverless workers