lambda-function-deployer
Deploys AWS Lambda functions with production-grade configuration: least-privilege execution IAM role, supported runtime selection, right-sized memory and timeout, KMS-encrypted environment variables, VPC configuration with NAT Gateway for internet access, dead-letter queues and on-failure destinations, provisioned vs on-demand concurrency, Lambda Layers, code signing with Signer, ECR image vs zip packaging, CloudWatch logging with retention, X-Ray tracing, and latest features (SnapStart, Web Adapter, response streaming). Emits a READY_TO_DEPLOY checklist with every configuration item verified. Use when creating a new Lambda function, deploying a function to production, validating a function configuration, or generating deployment commands and IaC templates. Triggers: create Lambda, deploy function, serverless, IAM role, VPC config, provisioned concurrency, layers, SnapStart, container image.
- License 许可
- Apache-2.0
- 最近更新
- 2026-09-24
- Stars
- ★ 4
- Forks
- 0
01 前言 Front Matter
- name
- lambda-function-deployer
- license
- Apache-2.0
- metadata
- { "tags": "aws, lambda, cloudops, deploy, serverless, compute, iam-role, vpc, concurrency, layers, code-signing, x-ray", "phase": "1", "author": "Jacky Chan — AWS Community Builder", "domain": "aws-cloudops", "family": "Compute", "version": "0.1.0", "keywords": "aws, lambda, cloudops, deploy, provisioning, serverless, compute, iam-role, runtime, vpc, concurrency, layers, code-signing, x-ray, snapstart", "task_type": "deploy", "complexity": "high", "entry_point": "false", "skill_class": "capability", "when_to_use": "Invoke when the user wants to create a new Lambda function, deploy a function to production, validate a function configuration against best practices, generate deployment CLI commands or IaC templates, or troubleshoot a deployment failure caused by missing prerequisites (IAM role, VPC, ECR image, KMS key). Do NOT invoke for ECS/Fargate deployments (use ecs-task-definition-auditor) or for Lambda runtime deprecation audits (use lambda-runtime-deprecation-auditor).", "dependencies": "aws-orchestrator", "requires_llm": "true", "verdict_shape": "READY_TO_DEPLOY | PREREQUISITES_MISSING", "supports_pipeline": "true" }
- description
- Deploys AWS Lambda functions with production-grade configuration: least-privilege execution IAM role, supported runtime selection, right-sized memory and timeout, KMS-encrypted environment variables, VPC configuration with NAT Gateway for internet access, dead-letter queues and on-failure destinations, provisioned vs on-demand concurrency, Lambda Layers, code signing with Signer, ECR image vs zip packaging, CloudWatch logging with retention, X-Ray tracing, and latest features (SnapStart, Web Adapter, response streaming). Emits a READY_TO_DEPLOY checklist with every configuration item verified. Use when creating a new Lambda function, deploying a function to production, validating a function configuration, or generating deployment commands and IaC templates. Triggers: create Lambda, deploy function, serverless, IAM role, VPC config, provisioned concurrency, layers, SnapStart, container image.
- compatibility
- Requires an LLM agent runtime (Claude Code, Cursor, Windsurf, Codex, Gemini). For live deployment: AWS CLI v2 with lambda, iam, kms, ec2, sqs, sns, ecr, logs, and signer access. Works with Terraform aws_lambda_function resources, CloudFormation AWS::Lambda::Function, and SAM templates.
02 资源文件 19
- 参考文档eval/test-cases.yaml6.4 KB
- 参考文档evals/baselines/deprecated-runtime-node14.md924 B
- 参考文档evals/baselines/full-correct-config.md1.5 KB
- 参考文档evals/baselines/java-snapstart-provisioned.md1.4 KB
- 参考文档evals/baselines/secure-api-backend.md1.3 KB
- 参考文档evals/baselines/vpc-no-nat-gateway.md996 B
- 参考文档evals/eval_config.yaml1.6 KB
- 参考文档evals/evals.json11.4 KB
- 参考文档evals/prompts/deprecated-runtime-node14.md384 B
- 参考文档evals/prompts/full-correct-config.md877 B
- 参考文档evals/prompts/java-snapstart-provisioned.md747 B
- 参考文档evals/prompts/secure-api-backend.md778 B
- 参考文档evals/prompts/vpc-no-nat-gateway.md569 B
- 参考文档example/README.md9.1 KB
- 参考文档references/advanced-patterns.md18.4 KB
- 参考文档references/deployment-cli-commands.md13.9 KB
- 参考文档references/diagnostic-commands.md3.2 KB
- 参考文档references/runtime-and-vpc-guide.md10.9 KB
- 参考文档skill.usf.yaml4.3 KB
03 SKILL.md 正文
Lambda Function Deployer
An AWS CloudOps agent skill that deploys AWS Lambda functions with correct production defaults. The skill walks the operator through a 13-step deployment procedure, explains why each default matters, and emits a READY_TO_DEPLOY checklist verifying every configuration item.
Activation keywords
create Lambda function, deploy Lambda, Lambda configuration, Lambda IAM role, execution role, AWSLambdaBasicExecutionRole, Lambda runtime, nodejs20.x, python3.12, java21, Lambda memory, Lambda timeout, Lambda VPC, NAT Gateway, Lambda DLQ, dead-letter queue, on-failure destination, provisioned concurrency, on-demand concurrency, Lambda layers, code signing, Lambda ECR, container image Lambda, CloudWatch Logs retention, X-Ray tracing, Lambda SnapStart, Lambda Web Adapter, response streaming.
Invocation contract (hard requirement)
When this skill is invoked with a Lambda deployment request (function
name, runtime, handler, workload type, or a partial existing
configuration), the agent MUST respond with the READY_TO_DEPLOY checklist
defined in §"Output format" using the literal all-caps labels FUNCTION:,
VERDICT:, CHECKLIST:, and VERIFICATION_COMMANDS:. Do NOT preface
the checklist with prose, headings, or disclaimers — emit the block as
the first lines of the response. This contract is what assertion-based
evals and downstream deployment pipelines rely on; deviating from the
literal labels breaks automation silently.
Reasoning framework (why the deployment order matters)
Full 13-item rationale moved to references/advanced-patterns.md —
see "Reasoning framework".
Prerequisites (verify before deployment)
| Prerequisite | Why it matters | How to verify |
|---|---|---|
| Function name | Must be unique within the account/region. 64-char max, alphanumeric + hyphens/underscores. | aws lambda list-functions --query 'Functions[].FunctionName' |
| Runtime | Must be a currently-supported runtime. Deprecated runtimes are force-upgraded or deactivated. | Check AWS Lambda runtimes documentation |
| Handler | Entry point format depends on runtime: file.function (Node/Python), class::method (Java/C#). |
Verify against the deployment package |
| Deployment package | Either a zip file (<= 50 MB) or an ECR image URI. | ls -la <zip> or aws ecr describe-images |
| Execution IAM role | Must exist with a trust policy allowing lambda.amazonaws.com to assume it. |
aws iam get-role --role-name <role> |
| KMS key (if env var encryption) | Customer-managed CMK with key policy granting the execution role kms:Decrypt. |
aws kms describe-key --key-id <alias> |
| VPC subnets + security group (if VPC) | Private subnets in at least 2 AZs + a security group allowing outbound to resources. NAT Gateway in a public subnet for internet access. | aws ec2 describe-subnets |
| SQS/SNS ARN (if DLQ/destination) | DLQ must exist before referencing it. The execution role needs sqs:SendMessage or sns:Publish on the ARN. |
aws sqs get-queue-url / aws sns get-topic-attributes |
| Layer ARNs (if layers) | Layers must exist in the same region (or be referenced by their full ARN with compatible architecture). | aws lambda list-layers |
| ECR image (if container deployment) | Image must be pushed to ECR, and the execution role needs ecr:BatchGetImage + ecr:GetDownloadUrlForLayer. |
aws ecr describe-images --repository-name <repo> |
| Signing profile (if code signing) | A signing profile in Signer + a code signing config in Lambda. | aws signer list-signing-profiles |
| IAM permissions | The caller needs lambda:CreateFunction, iam:PassRole on the execution role, and VPC/KMS/ECR permissions as applicable. |
aws sts get-caller-identity |
Deployment procedure (apply in order)
Step 1: Execution IAM role (least-privilege)
The execution role is the most critical configuration — it determines what the function can do. Create it BEFORE the function.
Trust/inline policy JSON, scoping note, service-specific permission table,
and least-privilege rule moved to references/advanced-patterns.md.
Step 2: Runtime selection
Choose a currently-supported runtime. AWS deprecates runtimes on a schedule — deprecated runtimes receive no security patches and are eventually force-upgraded or deactivated.
Currently supported runtimes (as of 2026):
| Runtime | Identifier | Notes |
|---|---|---|
| Node.js 20.x | nodejs20.x |
LTS, recommended for new JS/TS functions |
| Node.js 22.x | nodejs22.x |
Newer LTS |
| Python 3.12 | python3.12 |
Recommended for new Python functions |
| Python 3.13 | python3.13 |
Latest Python |
| Java 21 | java21 |
LTS, supports SnapStart |
| Java 17 | java17 |
LTS, supports SnapStart |
| .NET 8 | dotnet8 |
Current .NET LTS |
| Go 1.x | provided.al2023 |
Custom runtime with Go wrapper |
| Ruby 3.3 | ruby3.3 |
|
| provided.al2023 | provided.al2023 |
Custom runtime (Amazon Linux 2023) |
DEPRECATED runtimes to avoid: nodejs14.x, nodejs16.x,
nodejs18.x, python3.7, python3.8, python3.9, python3.10,
java8, java11, dotnet6, ruby2.7, go1.x (legacy). Deploying a
deprecated runtime is a deployment BLOCKER — flag as
PREREQUISITES_MISSING.
Step 3: Memory + timeout
Memory allocation ranges from 128 MB to 10,240 MB (10 GB). Lambda allocates CPU power proportionally: at 1,769 MB, the function gets 1 vCPU; at 3,538 MB, 2 vCPU. Memory is the primary performance lever.
Workload-based memory/timeout table, timeout rule, and CPU architecture
note moved to references/advanced-patterns.md (Step 3 deep dive).
Step 4: Environment variables + KMS encryption
Lambda encrypts environment variables at rest using AES-256 (AWS-managed key) by default. For sensitive variables (API keys, database credentials, tokens), use a customer-managed KMS key:
create-function CLI, KMS key-policy requirement, and secrets rule moved
to references/advanced-patterns.md (Step 4 deep dive).
Step 5: VPC configuration
Attach the function to a VPC when it needs to access private resources (RDS, ElastiCache, internal APIs, VPC-only services). VPC-attached functions CANNOT access the internet directly — they route through the VPC, which requires a NAT Gateway for internet access.
vpc-config CLI, subnet/SG/NAT rules, VPC endpoints, and ENI permission
notes moved to references/runtime-and-vpc-guide.md.
Step 6: Dead-letter queue + destinations
Asynchronous invocations (EventBridge, S3 events, SNS, direct
Invoke with InvocationType=Event) are retried on failure. Without a
DLQ or destination, failed events are silently discarded after the retry
limit.
DLQ/destination CLI, preference rationale, DLQ-vs-destination rule, and
sync-invocation note moved to references/advanced-patterns.md.
Step 7: Concurrency
On-demand/reserved/provisioned CLI and workflow moved to
references/advanced-patterns.md (Step 7 deep dive).
Concurrency scaling guidance:
| Workload | Concurrency model | Rationale |
|---|---|---|
| Event-driven (S3, EventBridge) | On-demand | Burst-tolerant, latency-insensitive |
| API backend (API Gateway) | Provisioned | Cold-start-sensitive, user-facing |
| Stream consumer (Kinesis, SQS) | Reserved (cap) | Prevent the function from consuming the entire account limit |
| Scheduled (EventBridge cron) | On-demand | Predictable, low-volume |
| High-throughput async pipeline | Reserved (minimum) + On-demand | Guarantee baseline, allow burst |
Step 8: Layers
Layers are shared archives containing dependencies, custom runtimes, or configuration. A function can reference up to 5 layers; the total unzipped deployment (function code + all layers) cannot exceed 250 MB.
Layers CLI, ordering rule, AWS-managed layers, and architecture match
moved to references/advanced-patterns.md (Step 8 deep dive).
Step 9: Code signing
For regulated environments (financial services, healthcare, government), code signing with AWS Signer ensures only trusted deployment packages are accepted.
Signing profile/config CLI and policy modes moved to
references/advanced-patterns.md (Step 9 deep dive).
Step 10: Packaging — zip vs ECR
Zip/Dockerfile/ECR CLI sequences and ECR pull permissions moved to
references/deployment-cli-commands.md (Step 10 deep dive).
Step 11: Logging (CloudWatch Logs retention)
Lambda automatically creates a log group /aws/lambda/<function-name>
on first invocation. There is NO default retention — logs accumulate
indefinitely. Always pre-create the log group with a retention policy:
Log-group creation and retention CLI moved to
references/deployment-cli-commands.md (Step 11 deep dive).
Retention guidance:
| Workload | Retention | Rationale |
|---|---|---|
| Production API | 30-90 days | Debugging + compliance window |
| Compliance (HIPAA, PCI) | 365+ days | Regulatory retention |
| Event-driven pipeline | 14-30 days | Operational debugging |
| Development / staging | 7-14 days | Cost control |
Step 12: Tracing (X-Ray)
Enable X-Ray tracing for end-to-end request visibility:
X-Ray CLI and daemon overhead note moved to
references/advanced-patterns.md (Step 12 deep dive).
Step 13: Verification
Full verification command listing moved to
references/diagnostic-commands.md (Step 13).
Latest Lambda features (2024-2026)
Feature list moved to references/advanced-patterns.md —
see "Latest Lambda features (2024-2026)".
Workload-specific deployment matrix
| Workload | Runtime | Memory | Timeout | VPC | Concurrency | DLQ/Dest | Tracing |
|---|---|---|---|---|---|---|---|
| API backend (API Gateway) | nodejs20.x / python3.12 | 512-1024 MB | 10-30s | If accessing private resources | Provisioned | On-failure destination | Active |
| Async event processor (S3/SQS/EventBridge) | python3.12 / java21 | 512-2048 MB | 60-300s | If accessing private resources | On-demand | On-failure destination | Active |
| Stream consumer (Kinesis/DynamoDB Streams) | nodejs20.x / python3.12 | 512-2048 MB | 60-300s | If accessing private resources | Reserved (cap) | N/A (stream handles retries) | Active |
| ML inference | python3.12 / provided.al2023 | 4096-10240 MB | 60-900s | No (GPU not supported) | Provisioned | On-failure destination | Active |
| Scheduled job (EventBridge cron) | nodejs20.x / python3.12 | 256-1024 MB | 60-900s | If accessing private resources | On-demand | On-failure destination | Optional |
| Java enterprise (Spring Boot) | java21 | 1024-2048 MB | 30-60s | If accessing private resources | Provisioned + SnapStart | On-failure destination | Active |
| Container function (> 50 MB) | provided.al2023 (ECR image) | 1024-4096 MB | 60-300s | If accessing private resources | Provisioned | On-failure destination | Active |
NEVER (anti-patterns)
-
NEVER deploy a function with
AdministratorAccessor*permissions on the execution role. The execution role is the function's identity — a compromised function with broad permissions can access every resource in the account. Scope permissions to the minimum required actions on the minimum required resources. -
NEVER deploy a deprecated runtime (
nodejs14.x,python3.7,java8,dotnet6, etc.). Deprecated runtimes receive no security patches and are force-upgraded or deactivated by AWS on the deprecation date, causing an outage. This is a deployment BLOCKER. -
NEVER attach a VPC-attached function to a PUBLIC subnet. Lambda creates Hyperplane ENIs in the specified subnets; public subnets cause routing issues. Always use PRIVATE subnets.
-
NEVER assume a VPC-attached function can access the internet. VPC routing applies — without a NAT Gateway (or VPC endpoint for AWS services), the function can reach VPC resources but NOT the internet. This is the #1 Lambda VPC deployment issue.
-
NEVER store secrets in plaintext environment variables. Environment variables are visible in the Lambda console, CloudTrail (
CreateFunction/UpdateFunctionConfigurationevents), and the function configuration API. Use Secrets Manager or SSM Parameter Store (SecureString) and retrieve at runtime via the execution role. -
NEVER omit CloudWatch Logs retention. Lambda creates the log group automatically but does NOT set a retention policy. Without retention, logs accumulate indefinitely, incurring unbounded cost. Always pre-create the log group with retention or set it post-deployment.
-
NEVER set provisioned concurrency on
$LATEST. Provisioned concurrency requires a published version or alias. Deploying provisioned concurrency on$LATESTis a silent no-op — the API accepts it but no environments are provisioned. -
NEVER set reserved concurrency to 0 unless you intentionally want to disable the function (emergency circuit-breaking). A reserved concurrency of 0 throttles ALL invocations.
-
NEVER mix layer architectures. Layers must match the function's architecture (
x86_64orarm64). An architecture mismatch causes deployment failure or runtimeexec format error. -
NEVER use
AWSLambdaBasicExecutionRole'slogs:CreateLogGrouponarn:aws:logs:*:*:*in production. This allows the function to create ANY log group in ANY region. Pre-create the log group and scope the role to just that group. -
NEVER skip X-Ray tracing for production microservice architectures. Without tracing, you cannot diagnose latency across service call chains. X-Ray is cheap (free tier + $5 per million traces) and the overhead is negligible for functions with >= 256 MB memory.
-
NEVER deploy an ECR-based function without verifying the execution role has ECR pull permissions. The function will fail at cold start with
ECRAccessDeniedException. Addecr:BatchGetImageandecr:GetDownloadUrlForLayerto the execution role or use a resource-based ECR policy. -
NEVER set a timeout longer than the workload needs. Lambda bills by execution duration (rounded up to the nearest 1ms). A function with a 900-second timeout that hangs will run (and bill) for 15 minutes per invocation. Set the timeout to P99 + 20% buffer.
-
NEVER use both a DLQ and an on-failure destination on the same function. Destinations supersede DLQs — having both is confusing and the DLQ will never receive messages. Use destinations for new deployments.
-
NEVER deviate from the checklist output format. Substituting
Verdict/**VERDICT**/### Verdict:for the literalVERDICT:label silently breaks downstream deployment pipelines and assertion-based evals.
Pre-flight safety checks (run before any deployment CLI)
Full pre-flight check listing (with CLI) moved to
references/diagnostic-commands.md.
Output format — MANDATORY literal labels
When invoked with a function deployment request, your ENTIRE response
MUST be the checklist block below. The labels are case-sensitive
all-caps keywords — write them EXACTLY as shown. Do NOT substitute
Verdict, **VERDICT**, ### Verdict, or any markdown variant. Do
NOT write a preamble ("Here is your deployment checklist…"). Start with
FUNCTION: and stop after the VERIFICATION_COMMANDS: block.
FUNCTION: <name>
VERDICT: READY_TO_DEPLOY | PREREQUISITES_MISSING
CHECKLIST:
[✓] Execution IAM role — least-privilege (scoped to function resources)
[✓] Runtime — nodejs20.x (supported, not deprecated)
[✓] Memory — 512 MB (right-sized for workload)
[✓] Timeout — 15s (P99 + 20% buffer)
[✓] Environment variables — KMS-encrypted (customer-managed CMK)
[OPTIONAL] VPC — Private subnets (2 AZs) + security group + NAT Gateway
[✓] Dead-letter / destination — On-failure SQS destination
[OPTIONAL] Concurrency — On-demand (no provisioned needed)
[OPTIONAL] Layers — Powertools for Python (v3)
[OPTIONAL] Code signing — Not configured
[✓] Packaging — Zip (12 MB compressed)
[✓] Logging — CloudWatch log group /aws/lambda/<name>, retention 30 days
[✓] Tracing — X-Ray Active mode
VERIFICATION_COMMANDS:
aws lambda get-function-configuration --function-name <name>
aws iam list-attached-role-policies --role-name <execution-role>
aws lambda get-function-event-invoke-config --function-name <name>
aws logs describe-log-groups --log-group-name-prefix /aws/lambda/<name>
aws lambda invoke --function-name <name> --payload '{}' /tmp/response.json
Status marker semantics:
[✓]— configuration is applied and verified.[✗]— configuration is NOT applied or is misconfigured. Cite the gap.[OPTIONAL]— recommended but not required for the workload type.[INPUT NEEDED]— a prerequisite value is missing (execution role ARN, KMS key ARN, VPC subnet IDs) and the operator must provide it before deployment can proceed.
PREREQUISITES_MISSING verdict: if any REQUIRED prerequisite is
missing (execution role, non-deprecated runtime, deployment package),
the verdict is PREREQUISITES_MISSING with each gap listed. The
checklist shows the target configuration with [INPUT NEEDED] or [✗]
for unmet prerequisites.
Worked example (copy the shape exactly):
FUNCTION: order-processor-prod
VERDICT: READY_TO_DEPLOY
CHECKLIST:
[✓] Execution IAM role — order-processor-exec (scoped to DynamoDB + SQS)
[✓] Runtime — python3.12
[✓] Memory — 1024 MB
[✓] Timeout — 30s
[✓] Environment variables — KMS-encrypted (alias/lambda-env-key)
[✓] VPC — Private subnets (subnet-aaa, subnet-bbb) + sg-order-processor + NAT Gateway
[✓] Destination — On-failure SQS (order-processing-dlq)
[✓] Concurrency — Reserved (50 concurrent executions)
[✓] Layers — Powertools for Python v3, AWS Parameters and Secrets
[OPTIONAL] Code signing — Not configured
[✓] Packaging — Zip (8 MB compressed)
[✓] Logging — /aws/lambda/order-processor-prod, retention 30 days
[✓] Tracing — X-Ray Active mode
VERIFICATION_COMMANDS:
aws lambda get-function-configuration --function-name order-processor-prod
aws iam list-attached-role-policies --role-name order-processor-exec
aws lambda get-function-event-invoke-config --function-name order-processor-prod
aws lambda get-function-concurrency --function-name order-processor-prod
aws logs describe-log-groups --log-group-name-prefix /aws/lambda/order-processor-prod
aws lambda invoke --function-name order-processor-prod --payload '{"test": true}' /tmp/response.json
Edge-case handling
Edge-case catalog moved to references/advanced-patterns.md —
see "Edge-case handling".
Recent AWS features (2024-2026)
Feature list moved to references/advanced-patterns.md —
see "Recent AWS features (2024-2026)".
References
-
references/deployment-cli-commands.md— full copy-pasteable CLI command sequence for all 13 deployment steps, including execution role creation, VPC setup, ECR build/push, code signing, and Terraformaws_lambda_functionresource equivalents. -
references/runtime-and-vpc-guide.md— deep reference on runtime support timelines (deprecation dates), VPC networking for Lambda (NAT Gateway vs VPC endpoints, Hyperplane ENI internals), SnapStart internals, and concurrency scaling limits.
Section taxonomy (CloudOps deployer pattern)
- Frontmatter — name, description, version, when-to-use.
- Activation keywords — discoverability terms.
- Invocation contract — the mandatory output format.
- Reasoning framework — the why behind the deployment order.
- Prerequisites — what must be verified before deployment.
- Deployment procedure — the ordered 13-step deployment sequence.
- Latest Lambda features — 2024-2026 feature changes.
- Workload-specific deployment matrix — per-workload configuration.
- NEVER — anti-patterns with explicit why each is wrong.
- Pre-flight safety checks — non-destructive deployment guards.
- Output format — the fixed checklist report shape.
- Edge-case handling — cross-account, SnapStart, VPC SDK calls.
- References — pointer to deeper references.
References (load on demand)
- advanced-patterns.md — reasoning framework, per-step deep dives (IAM, memory, KMS, DLQ, concurrency, layers, code signing, tracing), edge cases, recent AWS features.
- diagnostic-commands.md — Step 13 verification commands, pre-flight safety checks.
- deployment-cli-commands.md — packaging (zip/ECR) and logging CLI sequences.
- runtime-and-vpc-guide.md — VPC configuration rules and ENI permissions.
Domain
AWS CloudOps / Lambda Serverless Compute Provisioning.
AWS documentation
- AWS Lambda Developer Guide — https://docs.aws.amazon.com/lambda/latest/dg/welcome.html
- Lambda Configuration — https://docs.aws.amazon.com/lambda/latest/dg/configuration-console.html
- Lambda Execution Role — https://docs.aws.amazon.com/lambda/latest/dg/lambda-intro-execution-role.html
- Lambda VPC — https://docs.aws.amazon.com/lambda/latest/dg/configuration-vpc.html
- Lambda Runtimes — https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html
- Lambda SnapStart — https://docs.aws.amazon.com/lambda/latest/dg/snapstart.html
- Lambda Destinations — https://docs.aws.amazon.com/lambda/latest/dg/invocation-async.html
- Lambda Layers — https://docs.aws.amazon.com/lambda/latest/dg/configuration-layers.html
- Lambda Code Signing — https://docs.aws.amazon.com/lambda/latest/dg/configuration-codesigning.html
- Lambda CLI Reference — https://docs.aws.amazon.com/cli/latest/reference/lambda/
04 同仓库更多 Skills
xray-tracing-deployer
Deploys AWS X-Ray distributed tracing with production-grade configuration: X-Ray daemon deployment (EC2 systemd, ECS sidecar, EKS DaemonSet, Lambda built-in), SDK instrumentation (Java, Python, Node.js, Go, .NET) with annotations and metadata, sampling rules (default reservoir + rate vs custom rules with URL / method / service-name predicates), service map generation, trace query and retrieval, groups and insights, CloudWatch ServiceLens integration, IAM permissions (PutTraceSegments, GetSamplingRules), and latest features (Lambda Powertools tracing, OpenTelemetry / ADOT Collector support, W3C trace context). Emits a READY_TO_DEPLOY checklist with every configuration item verified. Use when enabling X-Ray on a new application, adding tracing to ECS / EKS / Lambda, validating a sampling configuration, or generating daemon deployment CLI and IaC templates. Triggers: X-Ray, distributed tracing, X-Ray daemon, sampling rules, service map, X-Ray SDK, OpenTelemetry, ADOT, Lambda Powertools, CloudWatch ServiceLens.
wellarchitected-workload-auditor
Audits AWS Well-Architected Tool workloads for review staleness, per-pillar high-risk issue counts, milestone tracking gaps, and remediation plan completeness. Emits a deterministic verdict (STALE_REVIEW | HIGH_RISK | CONFIG_GAP | OK) per workload with per-pillar risk breakdown, milestone trend analysis, and specific remediation. Use when reviewing Well-Architected workloads, checking WA review freshness, auditing high-risk issues per pillar, validating milestone coverage, or tracking remediation plans.
wellarchitected-review-operator
Operates AWS Well-Architected Tool reviews end-to-end — creates workloads, runs pillar reviews (operational excellence, security, reliability, performance, cost optimization, sustainability, Prosperity), answers questions with risk-tier rationale, generates reports and improvement plans, creates milestones, and integrates with Trusted Advisor and Well-Architected Labs. Runs deterministic pre-checks (workload existence, lens availability, pillar coverage), emits the exact update-answer / get-consolidated-report CLI behind a CONFIRM gate, and verifies risk-tier transitions. Emits READY | BLOCKED | COMPLETED. Use when creating a workload, answering pillar questions, generating an improvement plan, creating a milestone, or integrating with Trusted Advisor. Triggers: well-architected tool, well architected review, workload review, pillar, operational excellence, security, reliability, performance, cost optimization, sustainability, prosperity, improvement plan, milestone, trusted advisor.
wafv2-web-acl-deployer
Provisions AWS WAFv2 Web ACLs with correct production defaults: scope selection (CLOUDFRONT vs REGIONAL), managed rule groups (AWSManagedRulesCommonRuleSet, SQLiRuleSet, LinuxRuleSet, WindowsRuleSet, IPReputationList, BotControlRuleSet, AmazonIpReputationList, ATP), custom rules (byte match, IP set, regex pattern, geo match, size constraint, rate-based), rule priority ordering, logging destinations (Kinesis Firehose, CloudWatch Logs, S3), resource association (ALB, API Gateway, CloudFront), rate-based rules with aggregate keys (IP, forwarded IP), Challenge and CAPTCHA actions, and account takeover prevention. Emits a READY_TO_DEPLOY checklist. Use when creating a Web ACL, attaching managed rules, configuring rate limiting, enabling WAF logging, associating a Web ACL with an ALB/API Gateway/CloudFront, or configuring CAPTCHA/Challenge actions. Triggers: create WAF Web ACL, WAFv2, managed rule groups, WAF rate limiting, WAF logging, WAF CAPTCHA, WAF Challenge action, bot control, ATP managed rules.
wafv2-web-acl-auditor
Audits AWS WAFv2 Web ACL configurations to determine whether the ACL provides effective protection: default-action posture (Allow vs Block), managed-rule-group coverage gaps, rule effectiveness (BLOCK vs COUNT, shadow/bypass rules, stale exclusions), rate-based rule correctness, logging and visibility configuration, and text-transformation bypass vectors. Emits a deterministic verdict per Web ACL. Use when reviewing a WAFv2 Web ACL for security posture, checking managed-rule coverage, validating rate-limit configuration, auditing WAF logging, or hardening a WAF before production deployment. Triggers: WAF, WAFv2, Web ACL, managed rule group, AWSManagedRules, rate-based rule, CAPTCHA, Challenge, OverrideAction, Count mode, forwarded IP, Bot Control, ATP, text transformation, WAF logging, WAF visibility, OWASP, SQLi, XSS, RFI.
waf-rule-deployer
Provisions AWS WAFv2 rule sets with production defaults: Web ACL creation (CloudFront scope in us-east-1 vs Regional scope), rule groups (managed vs custom) with capacity planning in WCU (Web ACL Capacity Units, 1500 default per ACL), managed rule groups (AWSManagedRulesCommonRuleSet, AWSManagedRulesSQLiRuleSet, AWSManagedRulesAmazonIpReputationList, AWSManagedRulesLinuxRuleSet, AWSManagedRulesWindowsRuleSet, AWSManagedRulesUnixRuleSet), custom rules (byte-match, regex pattern set, geo-match, rate-based), IP set and regex pattern set resources, rule priority ordering (lowest number evaluated first), action types (allow, block, count, CAPTCHA, Challenge), bot control managed rule group, account takeover. Triggers: create WAF rule, WAF managed rule group, WAF custom rule, WAF byte match, WAF geo match, WAF rate based rule, WAF IP set, WAF regex pattern set, WAF WCU budget, WAF CloudFront ACL, WAF logging Kinesis Firehose, WAF bot control, WAF ATP, WAF label matching, WAF Challenge action, WAF CAPTCHA.