Skip to content

docs: Serverless Workers - Deploy guide (3/4)#4416

Open
lennessyy wants to merge 1 commit intofeat/serverless-worker-prereleasefrom
feat/serverless-worker-3-deploy
Open

docs: Serverless Workers - Deploy guide (3/4)#4416
lennessyy wants to merge 1 commit intofeat/serverless-worker-prereleasefrom
feat/serverless-worker-3-deploy

Conversation

@lennessyy
Copy link
Copy Markdown
Contributor

@lennessyy lennessyy commented Apr 8, 2026

Summary

  • Add production deployment docs for Serverless Workers under production-deployment/worker-deployments/serverless-workers/
    • index.mdx - Serverless Workers deploy overview
    • aws-lambda.mdx - AWS Lambda deployment guide
  • Update worker-deployments/index.mdx with serverless workers link
  • Add Serverless Workers category to sidebar under Worker Deployments
  • Set onBrokenLinks and onBrokenAnchors to warn (cross-references to pages in other split PRs)

Part 3 of 4 in splitting #4405 into smaller PRs.

Test plan

  • Verify the new pages render correctly in local dev
  • Confirm sidebar navigation shows Serverless Workers under Worker Deployments
  • Check that broken link warnings (not errors) appear for cross-PR references

🤖 Generated with Claude Code

┆Attachments: EDU-6188 docs: Serverless Workers - Deploy guide (3/4)

Add deploy guide for serverless workers covering AWS Lambda deployment,
including the serverless-workers index and aws-lambda pages under
production-deployment/worker-deployments. Update sidebar navigation
and set onBrokenLinks/onBrokenAnchors to warn for cross-PR references.

Part of #4405.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@lennessyy lennessyy requested a review from a team as a code owner April 8, 2026 23:50
@vercel
Copy link
Copy Markdown

vercel bot commented Apr 8, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
temporal-documentation Ready Ready Preview, Comment Apr 8, 2026 11:51pm

Request Review

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 8, 2026

📖 Docs PR preview links

## Prerequisites {#prerequisites}

- 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.
Copy link
Copy Markdown
Contributor Author

@lennessyy lennessyy Apr 8, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right now, I see that we need to add specific dynamic config parameters in Temporal server to enable this feature. When we ship, do self-hosted or cloud users need to do anything to enable it?

In the same vein, the WCI component readme mentions a scaling algorithm. Is this something users need to worry about? If so, what are the considerations? If not, can we still give a brief explanation of how it works and expected scaling behavior?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@smuneebahmad Let's sync on what we say about the self-managed scaling algo

The trust policy on the role includes an External ID condition to prevent [confused deputy](https://docs.aws.amazon.com/IAM/latest/UserGuide/confused-deputy.html) attacks.

Deploy the following CloudFormation template to create the invocation role and its permissions.

Copy link
Copy Markdown
Contributor Author

@lennessyy lennessyy Apr 8, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the UX design discussions we mentioned helping users create the roles using cloud formation templates. I haven't seen the template--is this still the plan?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants