[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A9PYAJREVTDGJT0C6DHTGX":3,"skill-same:01M7A9PYAJREVTDGJT0C6DHTGX":141},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":6,"ownerDescription":47,"updatedAt":48,"install":49,"resources":62},"01M7A9PYAJREVTDGJT0C6DHTGX","lambda-function-deployer",null,"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.","jhkchan\u002Faws-agent-skills","jhkchan","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1083902?v=4","01M7A2SVQYP9GQTPTDXP5JKYQ4","Jacky Chan","01M7A2SVS117YWCTZABB75HZR1",4,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Flambda-function-deployer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: lambda-function-deployer\ndescription: '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.'\nlicense: Apache-2.0\ncompatibility: '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.'\nmetadata:\n  domain: aws-cloudops\n  complexity: high\n  requires_llm: 'true'\n  phase: '1'\n  supports_pipeline: 'true'\n  entry_point: 'false'\n  family: Compute\n  task_type: deploy\n  skill_class: capability\n  verdict_shape: READY_TO_DEPLOY | PREREQUISITES_MISSING\n  version: 0.1.0\n  author: Jacky Chan — AWS Community Builder\n  tags: aws, lambda, cloudops, deploy, serverless, compute, iam-role, vpc, concurrency, layers, code-signing, x-ray\n  dependencies: aws-orchestrator\n  keywords: aws, lambda, cloudops, deploy, provisioning, serverless, compute, iam-role, runtime, vpc, concurrency, layers, code-signing, x-ray, snapstart\n  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\u002FFargate deployments (use ecs-task-definition-auditor) or for Lambda runtime deprecation audits (use lambda-runtime-deprecation-auditor).\n---\n\n# Lambda Function Deployer\n\nAn AWS CloudOps agent skill that deploys AWS Lambda functions with\ncorrect production defaults. The skill walks the operator through a\n13-step deployment procedure, explains why each default matters, and\nemits a READY_TO_DEPLOY checklist verifying every configuration item.\n\n## Activation keywords\n\ncreate Lambda function, deploy Lambda, Lambda configuration, Lambda IAM\nrole, execution role, AWSLambdaBasicExecutionRole, Lambda runtime,\nnodejs20.x, python3.12, java21, Lambda memory, Lambda timeout, Lambda\nVPC, NAT Gateway, Lambda DLQ, dead-letter queue, on-failure destination,\nprovisioned concurrency, on-demand concurrency, Lambda layers, code\nsigning, Lambda ECR, container image Lambda, CloudWatch Logs retention,\nX-Ray tracing, Lambda SnapStart, Lambda Web Adapter, response streaming.\n\n## Invocation contract (hard requirement)\n\nWhen this skill is invoked with a Lambda deployment request (function\nname, runtime, handler, workload type, or a partial existing\nconfiguration), the agent MUST respond with the READY_TO_DEPLOY checklist\ndefined in §\"Output format\" using the literal all-caps labels `FUNCTION:`,\n`VERDICT:`, `CHECKLIST:`, and `VERIFICATION_COMMANDS:`. Do NOT preface\nthe checklist with prose, headings, or disclaimers — emit the block as\nthe first lines of the response. This contract is what assertion-based\nevals and downstream deployment pipelines rely on; deviating from the\nliteral labels breaks automation silently.\n\n## Reasoning framework (why the deployment order matters)\n\nFull 13-item rationale moved to `references\u002Fadvanced-patterns.md` —\nsee \"Reasoning framework\".\n\n## Prerequisites (verify before deployment)\n\n| Prerequisite | Why it matters | How to verify |\n|---|---|---|\n| **Function name** | Must be unique within the account\u002Fregion. 64-char max, alphanumeric + hyphens\u002Funderscores. | `aws lambda list-functions --query 'Functions[].FunctionName'` |\n| **Runtime** | Must be a currently-supported runtime. Deprecated runtimes are force-upgraded or deactivated. | Check AWS Lambda runtimes documentation |\n| **Handler** | Entry point format depends on runtime: `file.function` (Node\u002FPython), `class::method` (Java\u002FC#). | Verify against the deployment package |\n| **Deployment package** | Either a zip file (\u003C= 50 MB) or an ECR image URI. | `ls -la \u003Czip>` or `aws ecr describe-images` |\n| **Execution IAM role** | Must exist with a trust policy allowing `lambda.amazonaws.com` to assume it. | `aws iam get-role --role-name \u003Crole>` |\n| **KMS key (if env var encryption)** | Customer-managed CMK with key policy granting the execution role `kms:Decrypt`. | `aws kms describe-key --key-id \u003Calias>` |\n| **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` |\n| **SQS\u002FSNS ARN (if DLQ\u002Fdestination)** | DLQ must exist before referencing it. The execution role needs `sqs:SendMessage` or `sns:Publish` on the ARN. | `aws sqs get-queue-url` \u002F `aws sns get-topic-attributes` |\n| **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` |\n| **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 \u003Crepo>` |\n| **Signing profile (if code signing)** | A signing profile in Signer + a code signing config in Lambda. | `aws signer list-signing-profiles` |\n| **IAM permissions** | The caller needs `lambda:CreateFunction`, `iam:PassRole` on the execution role, and VPC\u002FKMS\u002FECR permissions as applicable. | `aws sts get-caller-identity` |\n\n## Deployment procedure (apply in order)\n\n### Step 1: Execution IAM role (least-privilege)\n\nThe execution role is the most critical configuration — it determines\nwhat the function can do. Create it BEFORE the function.\n\nTrust\u002Finline policy JSON, scoping note, service-specific permission table,\nand least-privilege rule moved to `references\u002Fadvanced-patterns.md`.\n\n### Step 2: Runtime selection\n\nChoose a currently-supported runtime. AWS deprecates runtimes on a\nschedule — deprecated runtimes receive no security patches and are\neventually force-upgraded or deactivated.\n\n**Currently supported runtimes (as of 2026):**\n\n| Runtime | Identifier | Notes |\n|---|---|---|\n| Node.js 20.x | `nodejs20.x` | LTS, recommended for new JS\u002FTS functions |\n| Node.js 22.x | `nodejs22.x` | Newer LTS |\n| Python 3.12 | `python3.12` | Recommended for new Python functions |\n| Python 3.13 | `python3.13` | Latest Python |\n| Java 21 | `java21` | LTS, supports SnapStart |\n| Java 17 | `java17` | LTS, supports SnapStart |\n| .NET 8 | `dotnet8` | Current .NET LTS |\n| Go 1.x | `provided.al2023` | Custom runtime with Go wrapper |\n| Ruby 3.3 | `ruby3.3` | |\n| provided.al2023 | `provided.al2023` | Custom runtime (Amazon Linux 2023) |\n\n**DEPRECATED runtimes to avoid:** `nodejs14.x`, `nodejs16.x`,\n`nodejs18.x`, `python3.7`, `python3.8`, `python3.9`, `python3.10`,\n`java8`, `java11`, `dotnet6`, `ruby2.7`, `go1.x` (legacy). Deploying a\ndeprecated runtime is a deployment BLOCKER — flag as\nPREREQUISITES_MISSING.\n\n### Step 3: Memory + timeout\n\nMemory allocation ranges from 128 MB to 10,240 MB (10 GB). Lambda\nallocates CPU power proportionally: at 1,769 MB, the function gets\n1 vCPU; at 3,538 MB, 2 vCPU. Memory is the primary performance lever.\n\nWorkload-based memory\u002Ftimeout table, timeout rule, and CPU architecture\nnote moved to `references\u002Fadvanced-patterns.md` (Step 3 deep dive).\n\n### Step 4: Environment variables + KMS encryption\n\nLambda encrypts environment variables at rest using AES-256 (AWS-managed\nkey) by default. For sensitive variables (API keys, database credentials,\ntokens), use a customer-managed KMS key:\n\ncreate-function CLI, KMS key-policy requirement, and secrets rule moved\nto `references\u002Fadvanced-patterns.md` (Step 4 deep dive).\n\n\n### Step 5: VPC configuration\n\nAttach the function to a VPC when it needs to access private resources\n(RDS, ElastiCache, internal APIs, VPC-only services). **VPC-attached\nfunctions CANNOT access the internet directly** — they route through the\nVPC, which requires a NAT Gateway for internet access.\n\nvpc-config CLI, subnet\u002FSG\u002FNAT rules, VPC endpoints, and ENI permission\nnotes moved to `references\u002Fruntime-and-vpc-guide.md`.\n\n### Step 6: Dead-letter queue + destinations\n\n**Asynchronous invocations** (EventBridge, S3 events, SNS, direct\n`Invoke` with `InvocationType=Event`) are retried on failure. Without a\nDLQ or destination, failed events are silently discarded after the retry\nlimit.\n\nDLQ\u002Fdestination CLI, preference rationale, DLQ-vs-destination rule, and\nsync-invocation note moved to `references\u002Fadvanced-patterns.md`.\n\n### Step 7: Concurrency\n\nOn-demand\u002Freserved\u002Fprovisioned CLI and workflow moved to\n`references\u002Fadvanced-patterns.md` (Step 7 deep dive).\n\n**Concurrency scaling guidance:**\n\n| Workload | Concurrency model | Rationale |\n|---|---|---|\n| Event-driven (S3, EventBridge) | On-demand | Burst-tolerant, latency-insensitive |\n| API backend (API Gateway) | Provisioned | Cold-start-sensitive, user-facing |\n| Stream consumer (Kinesis, SQS) | Reserved (cap) | Prevent the function from consuming the entire account limit |\n| Scheduled (EventBridge cron) | On-demand | Predictable, low-volume |\n| High-throughput async pipeline | Reserved (minimum) + On-demand | Guarantee baseline, allow burst |\n\n### Step 8: Layers\n\nLayers are shared archives containing dependencies, custom runtimes, or\nconfiguration. A function can reference up to 5 layers; the total\nunzipped deployment (function code + all layers) cannot exceed 250 MB.\n\nLayers CLI, ordering rule, AWS-managed layers, and architecture match\nmoved to `references\u002Fadvanced-patterns.md` (Step 8 deep dive).\n\n### Step 9: Code signing\n\nFor regulated environments (financial services, healthcare, government),\ncode signing with AWS Signer ensures only trusted deployment packages\nare accepted.\n\nSigning profile\u002Fconfig CLI and policy modes moved to\n`references\u002Fadvanced-patterns.md` (Step 9 deep dive).\n\n### Step 10: Packaging — zip vs ECR\n\nZip\u002FDockerfile\u002FECR CLI sequences and ECR pull permissions moved to\n`references\u002Fdeployment-cli-commands.md` (Step 10 deep dive).\n\n### Step 11: Logging (CloudWatch Logs retention)\n\nLambda automatically creates a log group `\u002Faws\u002Flambda\u002F\u003Cfunction-name>`\non first invocation. **There is NO default retention — logs accumulate\nindefinitely.** Always pre-create the log group with a retention policy:\n\nLog-group creation and retention CLI moved to\n`references\u002Fdeployment-cli-commands.md` (Step 11 deep dive).\n\n**Retention guidance:**\n\n| Workload | Retention | Rationale |\n|---|---|---|\n| Production API | 30-90 days | Debugging + compliance window |\n| Compliance (HIPAA, PCI) | 365+ days | Regulatory retention |\n| Event-driven pipeline | 14-30 days | Operational debugging |\n| Development \u002F staging | 7-14 days | Cost control |\n\n### Step 12: Tracing (X-Ray)\n\nEnable X-Ray tracing for end-to-end request visibility:\n\nX-Ray CLI and daemon overhead note moved to\n`references\u002Fadvanced-patterns.md` (Step 12 deep dive).\n\n### Step 13: Verification\n\nFull verification command listing moved to\n`references\u002Fdiagnostic-commands.md` (Step 13).\n\n## Latest Lambda features (2024-2026)\n\nFeature list moved to `references\u002Fadvanced-patterns.md` —\nsee \"Latest Lambda features (2024-2026)\".\n\n## Workload-specific deployment matrix\n\n| Workload | Runtime | Memory | Timeout | VPC | Concurrency | DLQ\u002FDest | Tracing |\n|---|---|---|---|---|---|---|---|\n| **API backend** (API Gateway) | nodejs20.x \u002F python3.12 | 512-1024 MB | 10-30s | If accessing private resources | Provisioned | On-failure destination | Active |\n| **Async event processor** (S3\u002FSQS\u002FEventBridge) | python3.12 \u002F java21 | 512-2048 MB | 60-300s | If accessing private resources | On-demand | On-failure destination | Active |\n| **Stream consumer** (Kinesis\u002FDynamoDB Streams) | nodejs20.x \u002F python3.12 | 512-2048 MB | 60-300s | If accessing private resources | Reserved (cap) | N\u002FA (stream handles retries) | Active |\n| **ML inference** | python3.12 \u002F provided.al2023 | 4096-10240 MB | 60-900s | No (GPU not supported) | Provisioned | On-failure destination | Active |\n| **Scheduled job** (EventBridge cron) | nodejs20.x \u002F python3.12 | 256-1024 MB | 60-900s | If accessing private resources | On-demand | On-failure destination | Optional |\n| **Java enterprise** (Spring Boot) | java21 | 1024-2048 MB | 30-60s | If accessing private resources | Provisioned + SnapStart | On-failure destination | Active |\n| **Container function** (> 50 MB) | provided.al2023 (ECR image) | 1024-4096 MB | 60-300s | If accessing private resources | Provisioned | On-failure destination | Active |\n\n## NEVER (anti-patterns)\n\n- NEVER deploy a function with `AdministratorAccess` or `*` permissions\n  on the execution role. The execution role is the function's identity —\n  a compromised function with broad permissions can access every resource\n  in the account. Scope permissions to the minimum required actions on\n  the minimum required resources.\n\n- NEVER deploy a deprecated runtime (`nodejs14.x`, `python3.7`, `java8`,\n  `dotnet6`, etc.). Deprecated runtimes receive no security patches and\n  are force-upgraded or deactivated by AWS on the deprecation date,\n  causing an outage. This is a deployment BLOCKER.\n\n- NEVER attach a VPC-attached function to a PUBLIC subnet. Lambda creates\n  Hyperplane ENIs in the specified subnets; public subnets cause routing\n  issues. Always use PRIVATE subnets.\n\n- NEVER assume a VPC-attached function can access the internet. VPC\n  routing applies — without a NAT Gateway (or VPC endpoint for AWS\n  services), the function can reach VPC resources but NOT the internet.\n  This is the #1 Lambda VPC deployment issue.\n\n- NEVER store secrets in plaintext environment variables. Environment\n  variables are visible in the Lambda console, CloudTrail\n  (`CreateFunction` \u002F `UpdateFunctionConfiguration` events), and the\n  function configuration API. Use Secrets Manager or SSM Parameter Store\n  (SecureString) and retrieve at runtime via the execution role.\n\n- NEVER omit CloudWatch Logs retention. Lambda creates the log group\n  automatically but does NOT set a retention policy. Without retention,\n  logs accumulate indefinitely, incurring unbounded cost. Always\n  pre-create the log group with retention or set it post-deployment.\n\n- NEVER set provisioned concurrency on `$LATEST`. Provisioned concurrency\n  requires a published version or alias. Deploying provisioned\n  concurrency on `$LATEST` is a silent no-op — the API accepts it but\n  no environments are provisioned.\n\n- NEVER set reserved concurrency to 0 unless you intentionally want to\n  disable the function (emergency circuit-breaking). A reserved\n  concurrency of 0 throttles ALL invocations.\n\n- NEVER mix layer architectures. Layers must match the function's\n  architecture (`x86_64` or `arm64`). An architecture mismatch causes\n  deployment failure or runtime `exec format error`.\n\n- NEVER use `AWSLambdaBasicExecutionRole`'s `logs:CreateLogGroup` on\n  `arn:aws:logs:*:*:*` in production. This allows the function to create\n  ANY log group in ANY region. Pre-create the log group and scope the\n  role to just that group.\n\n- NEVER skip X-Ray tracing for production microservice architectures.\n  Without tracing, you cannot diagnose latency across service call chains.\n  X-Ray is cheap (free tier + $5 per million traces) and the overhead is\n  negligible for functions with >= 256 MB memory.\n\n- NEVER deploy an ECR-based function without verifying the execution role\n  has ECR pull permissions. The function will fail at cold start with\n  `ECRAccessDeniedException`. Add `ecr:BatchGetImage` and\n  `ecr:GetDownloadUrlForLayer` to the execution role or use a\n  resource-based ECR policy.\n\n- NEVER set a timeout longer than the workload needs. Lambda bills by\n  execution duration (rounded up to the nearest 1ms). A function with a\n  900-second timeout that hangs will run (and bill) for 15 minutes per\n  invocation. Set the timeout to P99 + 20% buffer.\n\n- NEVER use both a DLQ and an on-failure destination on the same\n  function. Destinations supersede DLQs — having both is confusing and\n  the DLQ will never receive messages. Use destinations for new\n  deployments.\n\n- NEVER deviate from the checklist output format. Substituting\n  `Verdict` \u002F `**VERDICT**` \u002F `### Verdict:` for the literal `VERDICT:`\n  label silently breaks downstream deployment pipelines and\n  assertion-based evals.\n\n## Pre-flight safety checks (run before any deployment CLI)\n\nFull pre-flight check listing (with CLI) moved to\n`references\u002Fdiagnostic-commands.md`.\n\n## Output format — MANDATORY literal labels\n\nWhen invoked with a function deployment request, your ENTIRE response\nMUST be the checklist block below. The labels are **case-sensitive\nall-caps keywords** — write them EXACTLY as shown. Do NOT substitute\n`Verdict`, `**VERDICT**`, `### Verdict`, or any markdown variant. Do\nNOT write a preamble (\"Here is your deployment checklist…\"). Start with\n`FUNCTION:` and stop after the `VERIFICATION_COMMANDS:` block.\n\n```text\nFUNCTION: \u003Cname>\nVERDICT: READY_TO_DEPLOY | PREREQUISITES_MISSING\nCHECKLIST:\n  [✓]      Execution IAM role — least-privilege (scoped to function resources)\n  [✓]      Runtime — nodejs20.x (supported, not deprecated)\n  [✓]      Memory — 512 MB (right-sized for workload)\n  [✓]      Timeout — 15s (P99 + 20% buffer)\n  [✓]      Environment variables — KMS-encrypted (customer-managed CMK)\n  [OPTIONAL] VPC — Private subnets (2 AZs) + security group + NAT Gateway\n  [✓]      Dead-letter \u002F destination — On-failure SQS destination\n  [OPTIONAL] Concurrency — On-demand (no provisioned needed)\n  [OPTIONAL] Layers — Powertools for Python (v3)\n  [OPTIONAL] Code signing — Not configured\n  [✓]      Packaging — Zip (12 MB compressed)\n  [✓]      Logging — CloudWatch log group \u002Faws\u002Flambda\u002F\u003Cname>, retention 30 days\n  [✓]      Tracing — X-Ray Active mode\nVERIFICATION_COMMANDS:\n  aws lambda get-function-configuration --function-name \u003Cname>\n  aws iam list-attached-role-policies --role-name \u003Cexecution-role>\n  aws lambda get-function-event-invoke-config --function-name \u003Cname>\n  aws logs describe-log-groups --log-group-name-prefix \u002Faws\u002Flambda\u002F\u003Cname>\n  aws lambda invoke --function-name \u003Cname> --payload '{}' \u002Ftmp\u002Fresponse.json\n```\n\n**Status marker semantics:**\n- `[✓]` — configuration is applied and verified.\n- `[✗]` — configuration is NOT applied or is misconfigured. Cite the gap.\n- `[OPTIONAL]` — recommended but not required for the workload type.\n- `[INPUT NEEDED]` — a prerequisite value is missing (execution role ARN,\n  KMS key ARN, VPC subnet IDs) and the operator must provide it before\n  deployment can proceed.\n\n**PREREQUISITES_MISSING verdict:** if any REQUIRED prerequisite is\nmissing (execution role, non-deprecated runtime, deployment package),\nthe verdict is `PREREQUISITES_MISSING` with each gap listed. The\nchecklist shows the target configuration with `[INPUT NEEDED]` or `[✗]`\nfor unmet prerequisites.\n\n**Worked example (copy the shape exactly):**\n\n```text\nFUNCTION: order-processor-prod\nVERDICT: READY_TO_DEPLOY\nCHECKLIST:\n  [✓]      Execution IAM role — order-processor-exec (scoped to DynamoDB + SQS)\n  [✓]      Runtime — python3.12\n  [✓]      Memory — 1024 MB\n  [✓]      Timeout — 30s\n  [✓]      Environment variables — KMS-encrypted (alias\u002Flambda-env-key)\n  [✓]      VPC — Private subnets (subnet-aaa, subnet-bbb) + sg-order-processor + NAT Gateway\n  [✓]      Destination — On-failure SQS (order-processing-dlq)\n  [✓]      Concurrency — Reserved (50 concurrent executions)\n  [✓]      Layers — Powertools for Python v3, AWS Parameters and Secrets\n  [OPTIONAL] Code signing — Not configured\n  [✓]      Packaging — Zip (8 MB compressed)\n  [✓]      Logging — \u002Faws\u002Flambda\u002Forder-processor-prod, retention 30 days\n  [✓]      Tracing — X-Ray Active mode\nVERIFICATION_COMMANDS:\n  aws lambda get-function-configuration --function-name order-processor-prod\n  aws iam list-attached-role-policies --role-name order-processor-exec\n  aws lambda get-function-event-invoke-config --function-name order-processor-prod\n  aws lambda get-function-concurrency --function-name order-processor-prod\n  aws logs describe-log-groups --log-group-name-prefix \u002Faws\u002Flambda\u002Forder-processor-prod\n  aws lambda invoke --function-name order-processor-prod --payload '{\"test\": true}' \u002Ftmp\u002Fresponse.json\n```\n\n## Edge-case handling\n\nEdge-case catalog moved to `references\u002Fadvanced-patterns.md` —\nsee \"Edge-case handling\".\n\n## Recent AWS features (2024-2026)\n\nFeature list moved to `references\u002Fadvanced-patterns.md` —\nsee \"Recent AWS features (2024-2026)\".\n\n## References\n\n- `references\u002Fdeployment-cli-commands.md` — full copy-pasteable CLI\n  command sequence for all 13 deployment steps, including execution role\n  creation, VPC setup, ECR build\u002Fpush, code signing, and Terraform\n  `aws_lambda_function` resource equivalents.\n\n- `references\u002Fruntime-and-vpc-guide.md` — deep reference on runtime\n  support timelines (deprecation dates), VPC networking for Lambda\n  (NAT Gateway vs VPC endpoints, Hyperplane ENI internals), SnapStart\n  internals, and concurrency scaling limits.\n\n## Section taxonomy (CloudOps deployer pattern)\n\n1. **Frontmatter** — name, description, version, when-to-use.\n2. **Activation keywords** — discoverability terms.\n3. **Invocation contract** — the mandatory output format.\n4. **Reasoning framework** — the *why* behind the deployment order.\n5. **Prerequisites** — what must be verified before deployment.\n6. **Deployment procedure** — the ordered 13-step deployment sequence.\n7. **Latest Lambda features** — 2024-2026 feature changes.\n8. **Workload-specific deployment matrix** — per-workload configuration.\n9. **NEVER** — anti-patterns with explicit *why* each is wrong.\n10. **Pre-flight safety checks** — non-destructive deployment guards.\n11. **Output format** — the fixed checklist report shape.\n12. **Edge-case handling** — cross-account, SnapStart, VPC SDK calls.\n13. **References** — pointer to deeper references.\n\n## References (load on demand)\n\n- [advanced-patterns.md](references\u002Fadvanced-patterns.md) — reasoning\n  framework, per-step deep dives (IAM, memory, KMS, DLQ, concurrency,\n  layers, code signing, tracing), edge cases, recent AWS features.\n- [diagnostic-commands.md](references\u002Fdiagnostic-commands.md) — Step 13\n  verification commands, pre-flight safety checks.\n- [deployment-cli-commands.md](references\u002Fdeployment-cli-commands.md) —\n  packaging (zip\u002FECR) and logging CLI sequences.\n- [runtime-and-vpc-guide.md](references\u002Fruntime-and-vpc-guide.md) — VPC\n  configuration rules and ENI permissions.\n\n## Domain\n\nAWS CloudOps \u002F Lambda Serverless Compute Provisioning.\n\n## AWS documentation\n\n- **AWS Lambda Developer Guide** — https:\u002F\u002Fdocs.aws.amazon.com\u002Flambda\u002Flatest\u002Fdg\u002Fwelcome.html\n- **Lambda Configuration** — https:\u002F\u002Fdocs.aws.amazon.com\u002Flambda\u002Flatest\u002Fdg\u002Fconfiguration-console.html\n- **Lambda Execution Role** — https:\u002F\u002Fdocs.aws.amazon.com\u002Flambda\u002Flatest\u002Fdg\u002Flambda-intro-execution-role.html\n- **Lambda VPC** — https:\u002F\u002Fdocs.aws.amazon.com\u002Flambda\u002Flatest\u002Fdg\u002Fconfiguration-vpc.html\n- **Lambda Runtimes** — https:\u002F\u002Fdocs.aws.amazon.com\u002Flambda\u002Flatest\u002Fdg\u002Flambda-runtimes.html\n- **Lambda SnapStart** — https:\u002F\u002Fdocs.aws.amazon.com\u002Flambda\u002Flatest\u002Fdg\u002Fsnapstart.html\n- **Lambda Destinations** — https:\u002F\u002Fdocs.aws.amazon.com\u002Flambda\u002Flatest\u002Fdg\u002Finvocation-async.html\n- **Lambda Layers** — https:\u002F\u002Fdocs.aws.amazon.com\u002Flambda\u002Flatest\u002Fdg\u002Fconfiguration-layers.html\n- **Lambda Code Signing** — https:\u002F\u002Fdocs.aws.amazon.com\u002Flambda\u002Flatest\u002Fdg\u002Fconfiguration-codesigning.html\n- **Lambda CLI Reference** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcli\u002Flatest\u002Freference\u002Flambda\u002F\n","# Lambda Function Deployer\n\nAn AWS CloudOps agent skill that deploys AWS Lambda functions with\ncorrect production defaults. The skill walks the operator through a\n13-step deployment procedure, explains why each default matters, and\nemits a READY_TO_DEPLOY checklist verifying every configuration item.\n\n## Activation keywords\n\ncreate Lambda function, deploy Lambda, Lambda configuration, Lambda IAM\nrole, execution role, AWSLambdaBasicExecutionRole, Lambda runtime,\nnodejs20.x, python3.12, java21, Lambda memory, Lambda timeout, Lambda\nVPC, NAT Gateway, Lambda DLQ, dead-letter queue, on-failure destination,\nprovisioned concurrency, on-demand concurrency, Lambda layers, code\nsigning, Lambda ECR, container image Lambda, CloudWatch Logs retention,\nX-Ray tracing, Lambda SnapStart, Lambda Web Adapter, response streaming.\n\n## Invocation contract (hard requirement)\n\nWhen this skill is invoked with a Lambda deployment request (function\nname, runtime, handler, workload type, or a partial existing\nconfiguration), the agent MUST respond with the READY_TO_DEPLOY checklist\ndefined in §\"Output format\" using the literal all-caps labels `FUNCTION:`,\n`VERDICT:`, `CHECKLIST:`, and `VERIFICATION_COMMANDS:`. Do NOT preface\nthe checklist with prose, headings, or disclaimers — emit the block as\nthe first lines of the response. This contract is what assertion-based\nevals and downstream deployment pipelines rely on; deviating from the\nliteral labels breaks automation silently.\n\n## Reasoning framework (why the deployment order matters)\n\nFull 13-item rationale moved to `references\u002Fadvanced-patterns.md` —\nsee \"Reasoning framework\".\n\n## Prerequisites (verify before deployment)\n\n| Prerequisite | Why it matters | How to verify |\n|---|---|---|\n| **Function name** | Must be unique within the account\u002Fregion. 64-char max, alphanumeric + hyphens\u002Funderscores. | `aws lambda list-functions --query 'Functions[].FunctionName'` |\n| **Runtime** | Must be a currently-supported runtime. Deprecated runtimes are force-upgraded or deactivated. | Check AWS Lambda runtimes documentation |\n| **Handler** | Entry point format depends on runtime: `file.function` (Node\u002FPython), `class::method` (Java\u002FC#). | Verify against the deployment package |\n| **Deployment package** | Either a zip file (\u003C= 50 MB) or an ECR image URI. | `ls -la \u003Czip>` or `aws ecr describe-images` |\n| **Execution IAM role** | Must exist with a trust policy allowing `lambda.amazonaws.com` to assume it. | `aws iam get-role --role-name \u003Crole>` |\n| **KMS key (if env var encryption)** | Customer-managed CMK with key policy granting the execution role `kms:Decrypt`. | `aws kms describe-key --key-id \u003Calias>` |\n| **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` |\n| **SQS\u002FSNS ARN (if DLQ\u002Fdestination)** | DLQ must exist before referencing it. The execution role needs `sqs:SendMessage` or `sns:Publish` on the ARN. | `aws sqs get-queue-url` \u002F `aws sns get-topic-attributes` |\n| **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` |\n| **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 \u003Crepo>` |\n| **Signing profile (if code signing)** | A signing profile in Signer + a code signing config in Lambda. | `aws signer list-signing-profiles` |\n| **IAM permissions** | The caller needs `lambda:CreateFunction`, `iam:PassRole` on the execution role, and VPC\u002FKMS\u002FECR permissions as applicable. | `aws sts get-caller-identity` |\n\n## Deployment procedure (apply in order)\n\n### Step 1: Execution IAM role (least-privilege)\n\nThe execution role is the most critical configuration — it determines\nwhat the function can do. Create it BEFORE the function.\n\nTrust\u002Finline policy JSON, scoping note, service-specific permission table,\nand least-privilege rule moved to `references\u002Fadvanced-patterns.md`.\n\n### Step 2: Runtime selection\n\nChoose a currently-supported runtime. AWS deprecates runtimes on a\nschedule — deprecated runtimes receive no security patches and are\neventually force-upgraded or deactivated.\n\n**Currently supported runtimes (as of 2026):**\n\n| Runtime | Identifier | Notes |\n|---|---|---|\n| Node.js 20.x | `nodejs20.x` | LTS, recommended for new JS\u002FTS functions |\n| Node.js 22.x | `nodejs22.x` | Newer LTS |\n| Python 3.12 | `python3.12` | Recommended for new Python functions |\n| Python 3.13 | `python3.13` | Latest Python |\n| Java 21 | `java21` | LTS, supports SnapStart |\n| Java 17 | `java17` | LTS, supports SnapStart |\n| .NET 8 | `dotnet8` | Current .NET LTS |\n| Go 1.x | `provided.al2023` | Custom runtime with Go wrapper |\n| Ruby 3.3 | `ruby3.3` | |\n| provided.al2023 | `provided.al2023` | Custom runtime (Amazon Linux 2023) |\n\n**DEPRECATED runtimes to avoid:** `nodejs14.x`, `nodejs16.x`,\n`nodejs18.x`, `python3.7`, `python3.8`, `python3.9`, `python3.10`,\n`java8`, `java11`, `dotnet6`, `ruby2.7`, `go1.x` (legacy). Deploying a\ndeprecated runtime is a deployment BLOCKER — flag as\nPREREQUISITES_MISSING.\n\n### Step 3: Memory + timeout\n\nMemory allocation ranges from 128 MB to 10,240 MB (10 GB). Lambda\nallocates CPU power proportionally: at 1,769 MB, the function gets\n1 vCPU; at 3,538 MB, 2 vCPU. Memory is the primary performance lever.\n\nWorkload-based memory\u002Ftimeout table, timeout rule, and CPU architecture\nnote moved to `references\u002Fadvanced-patterns.md` (Step 3 deep dive).\n\n### Step 4: Environment variables + KMS encryption\n\nLambda encrypts environment variables at rest using AES-256 (AWS-managed\nkey) by default. For sensitive variables (API keys, database credentials,\ntokens), use a customer-managed KMS key:\n\ncreate-function CLI, KMS key-policy requirement, and secrets rule moved\nto `references\u002Fadvanced-patterns.md` (Step 4 deep dive).\n\n\n### Step 5: VPC configuration\n\nAttach the function to a VPC when it needs to access private resources\n(RDS, ElastiCache, internal APIs, VPC-only services). **VPC-attached\nfunctions CANNOT access the internet directly** — they route through the\nVPC, which requires a NAT Gateway for internet access.\n\nvpc-config CLI, subnet\u002FSG\u002FNAT rules, VPC endpoints, and ENI permission\nnotes moved to `references\u002Fruntime-and-vpc-guide.md`.\n\n### Step 6: Dead-letter queue + destinations\n\n**Asynchronous invocations** (EventBridge, S3 events, SNS, direct\n`Invoke` with `InvocationType=Event`) are retried on failure. Without a\nDLQ or destination, failed events are silently discarded after the retry\nlimit.\n\nDLQ\u002Fdestination CLI, preference rationale, DLQ-vs-destination rule, and\nsync-invocation note moved to `references\u002Fadvanced-patterns.md`.\n\n### Step 7: Concurrency\n\nOn-demand\u002Freserved\u002Fprovisioned CLI and workflow moved to\n`references\u002Fadvanced-patterns.md` (Step 7 deep dive).\n\n**Concurrency scaling guidance:**\n\n| Workload | Concurrency model | Rationale |\n|---|---|---|\n| Event-driven (S3, EventBridge) | On-demand | Burst-tolerant, latency-insensitive |\n| API backend (API Gateway) | Provisioned | Cold-start-sensitive, user-facing |\n| Stream consumer (Kinesis, SQS) | Reserved (cap) | Prevent the function from consuming the entire account limit |\n| Scheduled (EventBridge cron) | On-demand | Predictable, low-volume |\n| High-throughput async pipeline | Reserved (minimum) + On-demand | Guarantee baseline, allow burst |\n\n### Step 8: Layers\n\nLayers are shared archives containing dependencies, custom runtimes, or\nconfiguration. A function can reference up to 5 layers; the total\nunzipped deployment (function code + all layers) cannot exceed 250 MB.\n\nLayers CLI, ordering rule, AWS-managed layers, and architecture match\nmoved to `references\u002Fadvanced-patterns.md` (Step 8 deep dive).\n\n### Step 9: Code signing\n\nFor regulated environments (financial services, healthcare, government),\ncode signing with AWS Signer ensures only trusted deployment packages\nare accepted.\n\nSigning profile\u002Fconfig CLI and policy modes moved to\n`references\u002Fadvanced-patterns.md` (Step 9 deep dive).\n\n### Step 10: Packaging — zip vs ECR\n\nZip\u002FDockerfile\u002FECR CLI sequences and ECR pull permissions moved to\n`references\u002Fdeployment-cli-commands.md` (Step 10 deep dive).\n\n### Step 11: Logging (CloudWatch Logs retention)\n\nLambda automatically creates a log group `\u002Faws\u002Flambda\u002F\u003Cfunction-name>`\non first invocation. **There is NO default retention — logs accumulate\nindefinitely.** Always pre-create the log group with a retention policy:\n\nLog-group creation and retention CLI moved to\n`references\u002Fdeployment-cli-commands.md` (Step 11 deep dive).\n\n**Retention guidance:**\n\n| Workload | Retention | Rationale |\n|---|---|---|\n| Production API | 30-90 days | Debugging + compliance window |\n| Compliance (HIPAA, PCI) | 365+ days | Regulatory retention |\n| Event-driven pipeline | 14-30 days | Operational debugging |\n| Development \u002F staging | 7-14 days | Cost control |\n\n### Step 12: Tracing (X-Ray)\n\nEnable X-Ray tracing for end-to-end request visibility:\n\nX-Ray CLI and daemon overhead note moved to\n`references\u002Fadvanced-patterns.md` (Step 12 deep dive).\n\n### Step 13: Verification\n\nFull verification command listing moved to\n`references\u002Fdiagnostic-commands.md` (Step 13).\n\n## Latest Lambda features (2024-2026)\n\nFeature list moved to `references\u002Fadvanced-patterns.md` —\nsee \"Latest Lambda features (2024-2026)\".\n\n## Workload-specific deployment matrix\n\n| Workload | Runtime | Memory | Timeout | VPC | Concurrency | DLQ\u002FDest | Tracing |\n|---|---|---|---|---|---|---|---|\n| **API backend** (API Gateway) | nodejs20.x \u002F python3.12 | 512-1024 MB | 10-30s | If accessing private resources | Provisioned | On-failure destination | Active |\n| **Async event processor** (S3\u002FSQS\u002FEventBridge) | python3.12 \u002F java21 | 512-2048 MB | 60-300s | If accessing private resources | On-demand | On-failure destination | Active |\n| **Stream consumer** (Kinesis\u002FDynamoDB Streams) | nodejs20.x \u002F python3.12 | 512-2048 MB | 60-300s | If accessing private resources | Reserved (cap) | N\u002FA (stream handles retries) | Active |\n| **ML inference** | python3.12 \u002F provided.al2023 | 4096-10240 MB | 60-900s | No (GPU not supported) | Provisioned | On-failure destination | Active |\n| **Scheduled job** (EventBridge cron) | nodejs20.x \u002F python3.12 | 256-1024 MB | 60-900s | If accessing private resources | On-demand | On-failure destination | Optional |\n| **Java enterprise** (Spring Boot) | java21 | 1024-2048 MB | 30-60s | If accessing private resources | Provisioned + SnapStart | On-failure destination | Active |\n| **Container function** (> 50 MB) | provided.al2023 (ECR image) | 1024-4096 MB | 60-300s | If accessing private resources | Provisioned | On-failure destination | Active |\n\n## NEVER (anti-patterns)\n\n- NEVER deploy a function with `AdministratorAccess` or `*` permissions\n  on the execution role. The execution role is the function's identity —\n  a compromised function with broad permissions can access every resource\n  in the account. Scope permissions to the minimum required actions on\n  the minimum required resources.\n\n- NEVER deploy a deprecated runtime (`nodejs14.x`, `python3.7`, `java8`,\n  `dotnet6`, etc.). Deprecated runtimes receive no security patches and\n  are force-upgraded or deactivated by AWS on the deprecation date,\n  causing an outage. This is a deployment BLOCKER.\n\n- NEVER attach a VPC-attached function to a PUBLIC subnet. Lambda creates\n  Hyperplane ENIs in the specified subnets; public subnets cause routing\n  issues. Always use PRIVATE subnets.\n\n- NEVER assume a VPC-attached function can access the internet. VPC\n  routing applies — without a NAT Gateway (or VPC endpoint for AWS\n  services), the function can reach VPC resources but NOT the internet.\n  This is the #1 Lambda VPC deployment issue.\n\n- NEVER store secrets in plaintext environment variables. Environment\n  variables are visible in the Lambda console, CloudTrail\n  (`CreateFunction` \u002F `UpdateFunctionConfiguration` events), and the\n  function configuration API. Use Secrets Manager or SSM Parameter Store\n  (SecureString) and retrieve at runtime via the execution role.\n\n- NEVER omit CloudWatch Logs retention. Lambda creates the log group\n  automatically but does NOT set a retention policy. Without retention,\n  logs accumulate indefinitely, incurring unbounded cost. Always\n  pre-create the log group with retention or set it post-deployment.\n\n- NEVER set provisioned concurrency on `$LATEST`. Provisioned concurrency\n  requires a published version or alias. Deploying provisioned\n  concurrency on `$LATEST` is a silent no-op — the API accepts it but\n  no environments are provisioned.\n\n- NEVER set reserved concurrency to 0 unless you intentionally want to\n  disable the function (emergency circuit-breaking). A reserved\n  concurrency of 0 throttles ALL invocations.\n\n- NEVER mix layer architectures. Layers must match the function's\n  architecture (`x86_64` or `arm64`). An architecture mismatch causes\n  deployment failure or runtime `exec format error`.\n\n- NEVER use `AWSLambdaBasicExecutionRole`'s `logs:CreateLogGroup` on\n  `arn:aws:logs:*:*:*` in production. This allows the function to create\n  ANY log group in ANY region. Pre-create the log group and scope the\n  role to just that group.\n\n- NEVER skip X-Ray tracing for production microservice architectures.\n  Without tracing, you cannot diagnose latency across service call chains.\n  X-Ray is cheap (free tier + $5 per million traces) and the overhead is\n  negligible for functions with >= 256 MB memory.\n\n- NEVER deploy an ECR-based function without verifying the execution role\n  has ECR pull permissions. The function will fail at cold start with\n  `ECRAccessDeniedException`. Add `ecr:BatchGetImage` and\n  `ecr:GetDownloadUrlForLayer` to the execution role or use a\n  resource-based ECR policy.\n\n- NEVER set a timeout longer than the workload needs. Lambda bills by\n  execution duration (rounded up to the nearest 1ms). A function with a\n  900-second timeout that hangs will run (and bill) for 15 minutes per\n  invocation. Set the timeout to P99 + 20% buffer.\n\n- NEVER use both a DLQ and an on-failure destination on the same\n  function. Destinations supersede DLQs — having both is confusing and\n  the DLQ will never receive messages. Use destinations for new\n  deployments.\n\n- NEVER deviate from the checklist output format. Substituting\n  `Verdict` \u002F `**VERDICT**` \u002F `### Verdict:` for the literal `VERDICT:`\n  label silently breaks downstream deployment pipelines and\n  assertion-based evals.\n\n## Pre-flight safety checks (run before any deployment CLI)\n\nFull pre-flight check listing (with CLI) moved to\n`references\u002Fdiagnostic-commands.md`.\n\n## Output format — MANDATORY literal labels\n\nWhen invoked with a function deployment request, your ENTIRE response\nMUST be the checklist block below. The labels are **case-sensitive\nall-caps keywords** — write them EXACTLY as shown. Do NOT substitute\n`Verdict`, `**VERDICT**`, `### Verdict`, or any markdown variant. Do\nNOT write a preamble (\"Here is your deployment checklist…\"). Start with\n`FUNCTION:` and stop after the `VERIFICATION_COMMANDS:` block.\n\n```text\nFUNCTION: \u003Cname>\nVERDICT: READY_TO_DEPLOY | PREREQUISITES_MISSING\nCHECKLIST:\n  [✓]      Execution IAM role — least-privilege (scoped to function resources)\n  [✓]      Runtime — nodejs20.x (supported, not deprecated)\n  [✓]      Memory — 512 MB (right-sized for workload)\n  [✓]      Timeout — 15s (P99 + 20% buffer)\n  [✓]      Environment variables — KMS-encrypted (customer-managed CMK)\n  [OPTIONAL] VPC — Private subnets (2 AZs) + security group + NAT Gateway\n  [✓]      Dead-letter \u002F destination — On-failure SQS destination\n  [OPTIONAL] Concurrency — On-demand (no provisioned needed)\n  [OPTIONAL] Layers — Powertools for Python (v3)\n  [OPTIONAL] Code signing — Not configured\n  [✓]      Packaging — Zip (12 MB compressed)\n  [✓]      Logging — CloudWatch log group \u002Faws\u002Flambda\u002F\u003Cname>, retention 30 days\n  [✓]      Tracing — X-Ray Active mode\nVERIFICATION_COMMANDS:\n  aws lambda get-function-configuration --function-name \u003Cname>\n  aws iam list-attached-role-policies --role-name \u003Cexecution-role>\n  aws lambda get-function-event-invoke-config --function-name \u003Cname>\n  aws logs describe-log-groups --log-group-name-prefix \u002Faws\u002Flambda\u002F\u003Cname>\n  aws lambda invoke --function-name \u003Cname> --payload '{}' \u002Ftmp\u002Fresponse.json\n```\n\n**Status marker semantics:**\n- `[✓]` — configuration is applied and verified.\n- `[✗]` — configuration is NOT applied or is misconfigured. Cite the gap.\n- `[OPTIONAL]` — recommended but not required for the workload type.\n- `[INPUT NEEDED]` — a prerequisite value is missing (execution role ARN,\n  KMS key ARN, VPC subnet IDs) and the operator must provide it before\n  deployment can proceed.\n\n**PREREQUISITES_MISSING verdict:** if any REQUIRED prerequisite is\nmissing (execution role, non-deprecated runtime, deployment package),\nthe verdict is `PREREQUISITES_MISSING` with each gap listed. The\nchecklist shows the target configuration with `[INPUT NEEDED]` or `[✗]`\nfor unmet prerequisites.\n\n**Worked example (copy the shape exactly):**\n\n```text\nFUNCTION: order-processor-prod\nVERDICT: READY_TO_DEPLOY\nCHECKLIST:\n  [✓]      Execution IAM role — order-processor-exec (scoped to DynamoDB + SQS)\n  [✓]      Runtime — python3.12\n  [✓]      Memory — 1024 MB\n  [✓]      Timeout — 30s\n  [✓]      Environment variables — KMS-encrypted (alias\u002Flambda-env-key)\n  [✓]      VPC — Private subnets (subnet-aaa, subnet-bbb) + sg-order-processor + NAT Gateway\n  [✓]      Destination — On-failure SQS (order-processing-dlq)\n  [✓]      Concurrency — Reserved (50 concurrent executions)\n  [✓]      Layers — Powertools for Python v3, AWS Parameters and Secrets\n  [OPTIONAL] Code signing — Not configured\n  [✓]      Packaging — Zip (8 MB compressed)\n  [✓]      Logging — \u002Faws\u002Flambda\u002Forder-processor-prod, retention 30 days\n  [✓]      Tracing — X-Ray Active mode\nVERIFICATION_COMMANDS:\n  aws lambda get-function-configuration --function-name order-processor-prod\n  aws iam list-attached-role-policies --role-name order-processor-exec\n  aws lambda get-function-event-invoke-config --function-name order-processor-prod\n  aws lambda get-function-concurrency --function-name order-processor-prod\n  aws logs describe-log-groups --log-group-name-prefix \u002Faws\u002Flambda\u002Forder-processor-prod\n  aws lambda invoke --function-name order-processor-prod --payload '{\"test\": true}' \u002Ftmp\u002Fresponse.json\n```\n\n## Edge-case handling\n\nEdge-case catalog moved to `references\u002Fadvanced-patterns.md` —\nsee \"Edge-case handling\".\n\n## Recent AWS features (2024-2026)\n\nFeature list moved to `references\u002Fadvanced-patterns.md` —\nsee \"Recent AWS features (2024-2026)\".\n\n## References\n\n- `references\u002Fdeployment-cli-commands.md` — full copy-pasteable CLI\n  command sequence for all 13 deployment steps, including execution role\n  creation, VPC setup, ECR build\u002Fpush, code signing, and Terraform\n  `aws_lambda_function` resource equivalents.\n\n- `references\u002Fruntime-and-vpc-guide.md` — deep reference on runtime\n  support timelines (deprecation dates), VPC networking for Lambda\n  (NAT Gateway vs VPC endpoints, Hyperplane ENI internals), SnapStart\n  internals, and concurrency scaling limits.\n\n## Section taxonomy (CloudOps deployer pattern)\n\n1. **Frontmatter** — name, description, version, when-to-use.\n2. **Activation keywords** — discoverability terms.\n3. **Invocation contract** — the mandatory output format.\n4. **Reasoning framework** — the *why* behind the deployment order.\n5. **Prerequisites** — what must be verified before deployment.\n6. **Deployment procedure** — the ordered 13-step deployment sequence.\n7. **Latest Lambda features** — 2024-2026 feature changes.\n8. **Workload-specific deployment matrix** — per-workload configuration.\n9. **NEVER** — anti-patterns with explicit *why* each is wrong.\n10. **Pre-flight safety checks** — non-destructive deployment guards.\n11. **Output format** — the fixed checklist report shape.\n12. **Edge-case handling** — cross-account, SnapStart, VPC SDK calls.\n13. **References** — pointer to deeper references.\n\n## References (load on demand)\n\n- [advanced-patterns.md](references\u002Fadvanced-patterns.md) — reasoning\n  framework, per-step deep dives (IAM, memory, KMS, DLQ, concurrency,\n  layers, code signing, tracing), edge cases, recent AWS features.\n- [diagnostic-commands.md](references\u002Fdiagnostic-commands.md) — Step 13\n  verification commands, pre-flight safety checks.\n- [deployment-cli-commands.md](references\u002Fdeployment-cli-commands.md) —\n  packaging (zip\u002FECR) and logging CLI sequences.\n- [runtime-and-vpc-guide.md](references\u002Fruntime-and-vpc-guide.md) — VPC\n  configuration rules and ENI permissions.\n\n## Domain\n\nAWS CloudOps \u002F Lambda Serverless Compute Provisioning.\n\n## AWS documentation\n\n- **AWS Lambda Developer Guide** — https:\u002F\u002Fdocs.aws.amazon.com\u002Flambda\u002Flatest\u002Fdg\u002Fwelcome.html\n- **Lambda Configuration** — https:\u002F\u002Fdocs.aws.amazon.com\u002Flambda\u002Flatest\u002Fdg\u002Fconfiguration-console.html\n- **Lambda Execution Role** — https:\u002F\u002Fdocs.aws.amazon.com\u002Flambda\u002Flatest\u002Fdg\u002Flambda-intro-execution-role.html\n- **Lambda VPC** — https:\u002F\u002Fdocs.aws.amazon.com\u002Flambda\u002Flatest\u002Fdg\u002Fconfiguration-vpc.html\n- **Lambda Runtimes** — https:\u002F\u002Fdocs.aws.amazon.com\u002Flambda\u002Flatest\u002Fdg\u002Flambda-runtimes.html\n- **Lambda SnapStart** — https:\u002F\u002Fdocs.aws.amazon.com\u002Flambda\u002Flatest\u002Fdg\u002Fsnapstart.html\n- **Lambda Destinations** — https:\u002F\u002Fdocs.aws.amazon.com\u002Flambda\u002Flatest\u002Fdg\u002Finvocation-async.html\n- **Lambda Layers** — https:\u002F\u002Fdocs.aws.amazon.com\u002Flambda\u002Flatest\u002Fdg\u002Fconfiguration-layers.html\n- **Lambda Code Signing** — https:\u002F\u002Fdocs.aws.amazon.com\u002Flambda\u002Flatest\u002Fdg\u002Fconfiguration-codesigning.html\n- **Lambda CLI Reference** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcli\u002Flatest\u002Freference\u002Flambda\u002F\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":40},{"tags":25,"phase":26,"author":27,"domain":28,"family":29,"version":30,"keywords":31,"task_type":32,"complexity":33,"entry_point":34,"skill_class":35,"when_to_use":36,"dependencies":37,"requires_llm":38,"verdict_shape":39,"supports_pipeline":38},"aws, lambda, cloudops, deploy, serverless, compute, iam-role, vpc, concurrency, layers, code-signing, x-ray","1","Jacky Chan — AWS Community Builder","aws-cloudops","Compute","0.1.0","aws, lambda, cloudops, deploy, provisioning, serverless, compute, iam-role, runtime, vpc, concurrency, layers, code-signing, x-ray, snapstart","deploy","high","false","capability","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\u002FFargate deployments (use ecs-task-definition-auditor) or for Lambda runtime deprecation audits (use lambda-runtime-deprecation-auditor).","aws-orchestrator","true","READY_TO_DEPLOY | PREREQUISITES_MISSING","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.","main","eeace51bd5dd1db2030729d83eeab988861553aa","skills\u002Flambda-function-deployer",0,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills","https:\u002F\u002Fgithub.com\u002Fjhkchan","CTO & Co-Founder @Beever-AI  & @votee. CAISP. AWS Community Builder. Organizer@GDGCloudHK. MongoDB Champion. Technopreneur + Infornographer.","2026-09-24 08:54:10",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add jhkchan\u002Faws-agent-skills --skill lambda-function-deployer",{"tool":55,"command":56},"bunx","bunx skills add jhkchan\u002Faws-agent-skills --skill lambda-function-deployer",{"tool":58,"command":59},"pnpm","pnpm dlx skills add jhkchan\u002Faws-agent-skills --skill lambda-function-deployer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Flambda-function-deployer\u002FSKILL.md",true,[63,69,73,77,81,85,89,93,97,101,105,109,113,117,121,125,129,133,137],{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"eval\u002Ftest-cases.yaml","REFERENCE","参考文档",6604,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Flambda-function-deployer\u002Feval\u002Ftest-cases.yaml",{"path":70,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":71,"sourceHtmlUrl":72},"evals\u002Fbaselines\u002Fdeprecated-runtime-node14.md",924,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Flambda-function-deployer\u002Fevals\u002Fbaselines\u002Fdeprecated-runtime-node14.md",{"path":74,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":75,"sourceHtmlUrl":76},"evals\u002Fbaselines\u002Ffull-correct-config.md",1534,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Flambda-function-deployer\u002Fevals\u002Fbaselines\u002Ffull-correct-config.md",{"path":78,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":79,"sourceHtmlUrl":80},"evals\u002Fbaselines\u002Fjava-snapstart-provisioned.md",1439,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Flambda-function-deployer\u002Fevals\u002Fbaselines\u002Fjava-snapstart-provisioned.md",{"path":82,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":83,"sourceHtmlUrl":84},"evals\u002Fbaselines\u002Fsecure-api-backend.md",1331,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Flambda-function-deployer\u002Fevals\u002Fbaselines\u002Fsecure-api-backend.md",{"path":86,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":87,"sourceHtmlUrl":88},"evals\u002Fbaselines\u002Fvpc-no-nat-gateway.md",996,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Flambda-function-deployer\u002Fevals\u002Fbaselines\u002Fvpc-no-nat-gateway.md",{"path":90,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":91,"sourceHtmlUrl":92},"evals\u002Feval_config.yaml",1652,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Flambda-function-deployer\u002Fevals\u002Feval_config.yaml",{"path":94,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":95,"sourceHtmlUrl":96},"evals\u002Fevals.json",11638,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Flambda-function-deployer\u002Fevals\u002Fevals.json",{"path":98,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":99,"sourceHtmlUrl":100},"evals\u002Fprompts\u002Fdeprecated-runtime-node14.md",384,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Flambda-function-deployer\u002Fevals\u002Fprompts\u002Fdeprecated-runtime-node14.md",{"path":102,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":103,"sourceHtmlUrl":104},"evals\u002Fprompts\u002Ffull-correct-config.md",877,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Flambda-function-deployer\u002Fevals\u002Fprompts\u002Ffull-correct-config.md",{"path":106,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":107,"sourceHtmlUrl":108},"evals\u002Fprompts\u002Fjava-snapstart-provisioned.md",747,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Flambda-function-deployer\u002Fevals\u002Fprompts\u002Fjava-snapstart-provisioned.md",{"path":110,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":111,"sourceHtmlUrl":112},"evals\u002Fprompts\u002Fsecure-api-backend.md",778,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Flambda-function-deployer\u002Fevals\u002Fprompts\u002Fsecure-api-backend.md",{"path":114,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":115,"sourceHtmlUrl":116},"evals\u002Fprompts\u002Fvpc-no-nat-gateway.md",569,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Flambda-function-deployer\u002Fevals\u002Fprompts\u002Fvpc-no-nat-gateway.md",{"path":118,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":119,"sourceHtmlUrl":120},"example\u002FREADME.md",9289,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Flambda-function-deployer\u002Fexample\u002FREADME.md",{"path":122,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":123,"sourceHtmlUrl":124},"references\u002Fadvanced-patterns.md",18795,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Flambda-function-deployer\u002Freferences\u002Fadvanced-patterns.md",{"path":126,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":127,"sourceHtmlUrl":128},"references\u002Fdeployment-cli-commands.md",14240,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Flambda-function-deployer\u002Freferences\u002Fdeployment-cli-commands.md",{"path":130,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":131,"sourceHtmlUrl":132},"references\u002Fdiagnostic-commands.md",3279,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Flambda-function-deployer\u002Freferences\u002Fdiagnostic-commands.md",{"path":134,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":135,"sourceHtmlUrl":136},"references\u002Fruntime-and-vpc-guide.md",11120,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Flambda-function-deployer\u002Freferences\u002Fruntime-and-vpc-guide.md",{"path":138,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":139,"sourceHtmlUrl":140},"skill.usf.yaml",4418,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Flambda-function-deployer\u002Fskill.usf.yaml",[142,149,156,163,170,177],{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":148,"publishedAt":19},"01M7ADVD60X4PCAPKSE58P9NDC","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 \u002F method \u002F 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 \u002F 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 \u002F EKS \u002F 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.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxray-tracing-deployer\u002FSKILL.md",[],[],{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":155,"publishedAt":19},"01M7ADTVJ7DCBM9CB1FY51GH7J","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.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwellarchitected-workload-auditor\u002FSKILL.md",[],[],{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":19},"01M7ADT59G6FTTNZYHT2QRPNNP","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 \u002F 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.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwellarchitected-review-operator\u002FSKILL.md",[],[],{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":169,"publishedAt":19},"01M7ADSH5JA9QHNPPHQCD7EVA7","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\u002FAPI Gateway\u002FCloudFront, or configuring CAPTCHA\u002FChallenge 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.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwafv2-web-acl-deployer\u002FSKILL.md",[],[],{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":176,"publishedAt":19},"01M7ADRYFAT8R73FBNCHRC573X","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\u002Fbypass 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.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwafv2-web-acl-auditor\u002FSKILL.md",[],[],{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":183,"publishedAt":19},"01M7ADR8W7G72JX4KFGN03QK8Q","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.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwaf-rule-deployer\u002FSKILL.md",[],[]]