aws/agent-toolkit-for-aws

aws-lambda-durable-functions

Builds resilient, long-running, multi-step applications with AWS Lambda durable functions with automatic state persistence, retry logic, and orchestration for long-running executions.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/aws/agent-toolkit-for-aws --skill aws-lambda-durable-functions

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

AWS Lambda durable functions

Durable functions are Lambda functions that checkpoint progress and can run multi-step workflows for up to one year, suspending without compute charges during waits and callbacks.

Use the developer guides for APIs

Do not write SDK method signatures, configuration objects, or IaC properties from memory. Read the relevant page first. The SDK guide covers TypeScript, Python, Java, Go, Rust, and C#, and the API names differ between languages.

AWS Durable Execution SDK Developer Guide:

TopicLink
Key concepts and quickstart<https://docs.aws.amazon.com/durable-execution/getting-started/key-concepts/>
Steps (retries, step semantics)<https://docs.aws.amazon.com/durable-execution/sdk-reference/operations/step/>
Waits<https://docs.aws.amazon.com/durable-execution/sdk-reference/operations/wait/>
Wait for condition (polling)<https://docs.aws.amazon.com/durable-execution/sdk-reference/operations/wait-for-condition/>
Callbacks and wait for callback<https://docs.aws.amazon.com/durable-execution/sdk-reference/operations/callback/>
Invoke (function chaining)<https://docs.aws.amazon.com/durable-execution/sdk-reference/operations/invoke/>
Parallel<https://docs.aws.amazon.com/durable-execution/sdk-reference/operations/parallel/>
Map (concurrency, completion policies)<https://docs.aws.amazon.com/durable-execution/sdk-reference/operations/map/>
Child contexts<https://docs.aws.amazon.com/durable-execution/sdk-reference/operations/child-context/>
Errors<https://docs.aws.amazon.com/durable-execution/sdk-reference/error-handling/errors/>
Retries<https://docs.aws.amazon.com/durable-execution/sdk-reference/error-handling/retries/>
Serialization<https://docs.aws.amazon.com/durable-execution/sdk-reference/state/serialization/>
Logging<https://docs.aws.amazon.com/durable-execution/sdk-reference/observability/logging/>
Python language guide<https://docs.aws.amazon.com/durable-execution/sdk-reference/languages/python/>
TypeScript language guide<https://docs.aws.amazon.com/durable-execution/sdk-reference/languages/typescript/>
Testing (local and cloud runners)<https://docs.aws.amazon.com/durable-execution/testing/>
Writing tests<https://docs.aws.amazon.com/durable-execution/testing/authoring/>
Test assertions<https://docs.aws.amazon.com/durable-execution/testing/assertions/>
Best practices (determinism, idempotency, state)<https://docs.aws.amazon.com/durable-execution/patterns/best-practices/>

Lambda durable functions guide, for the Lambda service side:

TopicLink
Deploying with CloudFormation, AWS CDK, AWS SAM, Terraform<https://docs.aws.amazon.com/lambda/latest/dg/durable-getting-started-iac.html>
Invoking (sync, async, execution names)<https://docs.aws.amazon.com/lambda/latest/dg/durable-invoking.html>
Security and permissions<https://docs.aws.amazon.com/lambda/latest/dg/durable-security.html>
Monitoring and execution history<https://docs.aws.amazon.com/lambda/latest/dg/durable-monitoring.html>
Best practices<https://docs.aws.amazon.com/lambda/latest/dg/durable-best-practices.html>
Supported runtimes<https://docs.aws.amazon.com/lambda/latest/dg/durable-supported-runtimes.html>

Works best with the AWS MCP Server for reading these pages, but it is not required.

Critical rules: Lambda

  1. Durable execution is enabled only when a function is created. It cannot be added to an existing function. Create a new function with durable execution (DurableConfig in IaC) and move the logic into it.
  2. The handler must be wrapped with the SDK (withDurableExecution in TypeScript, @durable_execution in Python). A plain handler deployed to a durable function fails every execution, so when moving existing code, wrap it rather than copying it unchanged.
  3. Invoke with a qualified ARN: a version, an alias, or $LATEST (for example my-function:live). An unqualified function name fails.
  4. The execution role needs `lambda:CheckpointDurableExecution`, `lambda:GetDurableExecutionState`, and CloudWatch Logs permissions. The managed policy AWSLambdaBasicDurableExecutionRolePolicy grants these on all resources and is fine for getting started; for production, use a policy scoped to the function's ARN. Durable invokes also need lambda:InvokeFunction on the target. External systems that complete callbacks need lambda:SendDurableExecutionCallbackSuccess and lambda:SendDurableExecutionCallbackFailure, plus lambda:SendDurableExecutionCallbackHeartbeat if they send heartbeats.

Critical rules: the replay model

Durable functions use checkpoint and replay. After a wait, failure, or resume, the handler re-runs from the beginning. Completed operations return their checkpointed results without re-executing, and code outside operations runs again on every replay.

  1. Code outside steps must be deterministic. Put timestamps, random values, UUIDs, API calls, and database queries in a step.
  2. Never call durable operations inside a step. Use a child context to group operations.
  3. Closure mutations inside steps are lost on replay. Return values from steps instead.
  4. Side effects outside steps repeat on every replay. Put them in steps. The context logger is replay-aware and safe anywhere.
  5. Don't sleep in the handler. Use a durable wait or callback, which suspends the execution without compute charges.
  6. For human approval or an external job that can report back, use wait for callback (waitForCallback / wait_for_callback). Use wait for condition only when the external system can only be polled.
  7. For sagas, run compensations as named steps, in reverse order, from the catch block around the forward steps.
  8. Steps default to at-least-once (`AtLeastOncePerRetry`), so a crash before the checkpoint re-runs the step. For non-idempotent calls, say so and use AtMostOncePerRetry with retries disabled or an idempotency key.
  9. Express map and parallel failure tolerance in the form the user gives it. A percentage becomes a tolerated failure percentage in the completion config, not a computed count.

When the user asks for code, a test, or a template, show it inline in your answer, even if you also write it to a file. When writing or reviewing durable function code, check it against these rules. When writing tests, name every operation and look operations up by name, not by index.

Troubleshooting executions

Diagnosis is read-only. Read the execution and its history (aws lambda get-durable-execution, aws lambda get-durable-execution-history) and report what you find. Never stop an execution or change its state unless the user explicitly asks.

Security

  • Step results and callback payloads are checkpointed. Do not return secrets, credentials, or PII from steps. Store them in Secrets Manager or SSM Parameter Store, retrieve them inside steps, and return references.
  • Validate event payloads at the handler entry point, and validate callback payloads, which come from external systems.
  • Encrypt the function's CloudWatch Logs log group with KMS, and avoid DEBUG logging outside development because it can expose step results.

When the guides and the SDK disagree

Trust the installed SDK source and tell the user about the discrepancy.

같은 저장소의 Skills

더 많은 Skills

모든 Skills
aws
공식

deploying-containers-to-amazon-lightsail

Deploys, hosts, or runs a container or Docker app on Amazon Lightsail Container Service and returns a live, managed HTTPS URL at a flat monthly price — no cluster, VPC, load balancer, or registry to set up. Used when deploying a container image to Lightsail from a local Docker build, a public registry image, or a GitHub repo, or when a Lightsail container deployment fails or won't serve — including when the request doesn't name Lightsail but asks to run one always-on container behind a public UR

1시간 설치 수
4
GitHub Stars
3.5천
업데이트
11월 20일
aws
공식

managing-data-asset-access

Grants, requests, audits and removes access to data assets in an AWS data catalog (the Amazon SageMaker Catalog supported by Amazon DataZone) through catalog subscriptions over published listings. Covers requesting a subscription, approving or rejecting requests with a recorded decision, sharing a listing with a project, revoking one or many subscriptions, and confirming grant settlement. Triggers on: give another team access to a table, request access to a dataset, approve or reject an access r

1시간 설치 수
4
GitHub Stars
3.5천
업데이트
11월 20일
aws
공식

managing-data-catalog

Writes and curates business metadata in an AWS data catalog: the Amazon SageMaker Catalog (Amazon DataZone), or the AWS Glue Data Catalog. Detects which catalog platform an account uses before writing. Triggers on: add a description to a table, document a dataset, write a README, set an owner, add column comments, tag with a glossary term, create a business glossary, create a metadata form, publish an asset, create a data product, run the data source crawl, delete a catalog asset, attach a conve

1시간 설치 수
4
GitHub Stars
3.5천
업데이트
11월 20일
aws
공식

aws-billing-and-cost-management

Analyze AWS costs, find savings, manage budgets, evaluate Savings Plans and Reserved Instances, right-size EC2/Lambda/RDS/EBS with Compute Optimizer, look up service pricing, query CUR with Athena, detect cost anomalies, scope costs to billing views, and monitor Free Tier usage. Triggers on: AWS bill, cost analysis, reduce spend, savings plan, reserved instance, right-size, budget alert, cost optimization, pricing, free tier, cost anomaly, CUR, cost audit, billing view, billing view ARN.

1시간 설치 수
2
GitHub Stars
3.5천
업데이트
11월 19일