[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AD419X94J4B5XMJD6VF0PR":3,"skill-same:01M7AD419X94J4B5XMJD6VF0PR":152},{"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":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":6,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M7AD419X94J4B5XMJD6VF0PR","stepfunctions-express-deployer",null,"Provisions Step Functions Express Workflows with production defaults: Express-vs-Standard decision (5-min cap, at-least-once vs exactly-once, per-invocation vs per-transition pricing), sync (RequestResponse) vs async invocation, CloudWatch Logs configuration (ALL \u002F ERROR \u002F FATAL \u002F OFF levels and INCLUDE_DATA \u002F EXCLUDE_DATA), IAM least-privilege execution role, EventBridge scheduling, Distributed Map and Inline Map fan-out, Express-compatible service integrations (.sync, AWS SDK direct calls), idempotency for at-least-once delivery, observability (metrics, X-Ray, CloudWatch alarms). Emits READY_TO_DEPLOY \u002F PREREQUISITES_MISSING with copy-pasteable stepfunctions \u002F logs \u002F events \u002F iam CLI. Use when provisioning an Express workflow, migrating high-volume Standard workloads to Express, configuring sync invocation from API Gateway, or hardening logging. Triggers: Express workflow, create state machine EXPRESS, sync express, async express, EventBridge Step Functions, Step Functions logging, Distributed Map Express.","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\u002Fstepfunctions-express-deployer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: stepfunctions-express-deployer\ndescription: 'Provisions Step Functions Express Workflows with production defaults: Express-vs-Standard decision (5-min cap, at-least-once vs exactly-once, per-invocation vs per-transition pricing), sync (RequestResponse) vs async invocation, CloudWatch Logs configuration (ALL \u002F ERROR \u002F FATAL \u002F OFF levels and INCLUDE_DATA \u002F EXCLUDE_DATA), IAM least-privilege execution role, EventBridge scheduling, Distributed Map and Inline Map fan-out, Express-compatible service integrations (.sync, AWS SDK direct calls), idempotency for at-least-once delivery, observability (metrics, X-Ray, CloudWatch alarms). Emits READY_TO_DEPLOY \u002F PREREQUISITES_MISSING with copy-pasteable stepfunctions \u002F logs \u002F events \u002F iam CLI. Use when provisioning an Express workflow, migrating high-volume Standard workloads to Express, configuring sync invocation from API Gateway, or hardening logging. Triggers: Express workflow, create state machine EXPRESS, sync express, async express, EventBridge Step Functions, Step Functions logging, Distributed Map Express.'\nlicense: Apache-2.0\ncompatibility: Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). Live provisioning uses AWS CLI v2 with stepfunctions (create-state-machine, update-state-machine, describe-state-machine, start-sync-execution, start-execution, validate-state-machine-definition), logs (create-log-group, put-retention-policy), events (put-rule, put-targets), iam (create-role, attach-role-policy, put-role-policy), and cloudformation \u002F terraform aws_sfn_state_machine equivalents.\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: AppIntegration\n  task_type: deploy\n  skill_class: capability\n  lifecycle_status: active\n  verdict_shape: READY_TO_DEPLOY | PREREQUISITES_MISSING\n  when_to_use: Provisioning a new Step Functions Express Workflow, deciding between Express and Standard (5-min cap, at-least-once semantics, per-invocation pricing), configuring sync (RequestResponse) vs async invocation, attaching a CloudWatch Logs log group with the correct level (ALL \u002F ERROR \u002F FATAL \u002F OFF) and INCLUDE_DATA \u002F EXCLUDE_DATA exposure, scheduling recurring Express executions via EventBridge, using Distributed Map or Inline Map with Express, using .sync service integrations (Glue, Batch, ECS, SageMaker), or hardening idempotency for at-least-once delivery. Do NOT invoke for Standard workflows that run >5 minutes or use .waitForTaskToken (use stepfunctions-statemachine-deployer), or for troubleshooting execution failures (use stepfunctions-execution-troubleshooter).\n  activation_triggers: Express workflow, create Express state machine, Step Functions EXPRESS, sync express execution, start-sync-execution, async express, Express workflow logging, Step Functions CloudWatch Logs, INCLUDE_DATA, EXCLUDE_DATA, EventBridge Step Functions, Distributed Map Express, Standard-to-Express migration, Express idempotency\n  invocation_schema: 'Input: either (a) a workflow name + ASL definition (or requirements to derive one) + sync\u002Fasync invocation mode, or (b) a Standard-to-Express migration spec (existing state machine ARN + compatibility check), or (c) an EventBridge-scheduled Express spec (schedule expression + execution role). Output: deterministic EXPRESS_WORKFLOW \u002F VERDICT \u002F CHECKLIST \u002F VERIFICATION_COMMANDS block per the STRICT output contract, where VERDICT is READY_TO_DEPLOY or PREREQUISITES_MISSING.'\n  version: 0.1.0\n  author: Jacky Chan — AWS Community Builder\n  keywords: aws, step-functions, stepfunctions, express-workflow, state-machine, asl, amazon-states-language, sync-execution, requestresponse, async-execution, cloudwatch-logs, include-data, exclude-data, eventbridge, distributed-map, inline-map, sync-integration, waitfortasktoken, idempotency, at-least-once, iam-execution-role, x-ray, cloudops, deploy\n  tags: aws, step-functions, express-workflow, state-machine, sync-execution, logging, eventbridge, deploy, app-integration\n  dependencies: aws-orchestrator\n---\n\n# Step Functions Express Workflows Deployer\n\n## What this skill does\n\nProvisions Step Functions Express Workflows and surrounding\nprimitives (CloudWatch Logs with correct level and data-exposure,\nIAM least-privilege execution role, EventBridge scheduling,\nDistributed Map configuration, idempotency guard for at-least-once\ndelivery) with production defaults. The skill walks a 9-step\nprocedure, surfaces the silent-failure modes unique to Express\n(most dangerous: `.waitForTaskToken` is rejected at create-time,\nbut operators migrating from Standard discover this only on deploy;\nlogging is NOT enabled by default, so async Express executions are\ninvisible after the 5-minute history window; the at-least-once\ndelivery model means non-idempotent Lambda handlers can double-\nexecute on retries). The single most common incident this skill\nprevents: an operator migrates a high-volume Standard workflow to\nExpress for cost savings, the migration drops CloudWatch Logs, and\nthe first failed execution is invisible — no alarm, no log, and the\n5-minute execution history has already rolled over.\n\n## Quick navigation\n\n| Section | What it covers | When to read it |\n|---|---|---|\n| **Quick reference** | Provisioning summary (9 steps), verdict thresholds | Before any operation |\n| **Activation keywords** | Phrases that route to this skill | Disambiguating routing |\n| **Reasoning framework** | Why Express is a cost + semantics decision | Choosing Express vs Standard |\n| **Dependency graph** | Which configs silently no-op without their prerequisite | Debugging \"logs are empty\" |\n| **Expert heuristic** | waitForTaskToken block; at-least-once idempotency; sync API Gateway timeouts | Pre-empt incidents |\n| **Prerequisites** | What to verify before emitting any command | Avoid PREREQUISITES_MISSING rework |\n| **9-step procedure** | The actual provisioning with copy-pasteable CLI | Executing the deploy |\n| **NEVER (top 5)** | Hard rules that prevent silent exposure \u002F data-plane bugs | Review before deploy |\n| **STRICT output contract** | Required EXPRESS_WORKFLOW \u002F VERDICT \u002F CHECKLIST \u002F VERIFICATION_COMMANDS block | Formatting the response |\n| **Recent AWS features** | Express + Distributed Map, AWS SDK direct calls | Stay current |\n\n## Quick reference — provisioning summary (9 steps)\n\n| Step | Action | Reversible? | Key risk if skipped |\n|---|---|---|---|\n| 1 | Confirm Express-vs-Standard decision (5-min cap, at-least-once, cost model) | — | wrong type = 100x cost or 5-min timeout |\n| 2 | Verify workflow duration fits in the 5-minute Express cap | Yes | sync API Gateway returns 500; async retried mid-flight |\n| 3 | Verify all service integrations are Express-compatible (NO `.waitForTaskToken`) | Yes | create-state-machine API silently rejects the definition |\n| 4 | Define the ASL with Express-compatible patterns (Distributed Map, .sync, AWS SDK) | Yes | — |\n| 5 | Create the IAM execution role with least-privilege | Yes | over-broad `states:*` on `*` |\n| 6 | Configure logging (CloudWatch Logs + level + INCLUDE_DATA\u002FEXCLUDE_DATA) | Yes | async executions invisible after 5-min history |\n| 7 | Choose sync (RequestResponse) vs async invocation mode | Yes | sync API Gateway timeout misalignment |\n| 8 | Configure EventBridge scheduling + observability (X-Ray, CloudWatch alarms) | Yes | silent failures with no alarm |\n| 9 | Verify every configuration item against actual state + emit checklist | — | silent no-ops |\n\n**Critical ordering constraints:** Express-vs-Standard decision\nfirst (every downstream choice depends on the type); duration\nbudget before ASL definition (a workflow that exceeds 5 minutes\ncannot be Express); integration compatibility before the IAM role\n(`.waitForTaskToken` rejected at create-time even with a valid\nrole); logging configuration before the first execution (without\nlogging, async Express executions are invisible after the 5-minute\nhistory rolls over); sync-vs-async choice before the caller\nintegration (API Gateway sync requires timeout alignment to ≤ 29s\nto avoid 504). Rationale and the silent-failure table are below.\n\n## Activation keywords\n\nExpress workflow, create Express state machine, Step Functions\nEXPRESS, sync express execution, start-sync-execution, async\nexpress, Express workflow logging, Step Functions CloudWatch Logs,\nINCLUDE_DATA, EXCLUDE_DATA, FATAL \u002F ERROR \u002F ALL levels, EventBridge\nStep Functions target, Distributed Map Express, Inline Map Express,\nStandard-to-Express migration, at-least-once Step Functions, Express\nidempotency, Express sync API Gateway, .sync integration Express,\nAWS SDK integration, X-Ray tracing Step Functions.\n\n## Invocation contract (hard requirement)\n\nWhen this skill is invoked with an Express Workflow provisioning\nrequest, the agent MUST respond with the checklist defined in\n§\"STRICT output contract\" using the literal all-caps labels\n`EXPRESS_WORKFLOW:`, `VERDICT:`, `CHECKLIST:`, and\n`VERIFICATION_COMMANDS:`. Do NOT preface the checklist with prose,\nheadings, or disclaimers — emit the block as the first lines of the\nresponse. This contract is what assertion-based evals and downstream\nprovisioning pipelines rely on; deviating from the literal labels\nbreaks automation silently.\n\n## Reasoning framework (why the Express decision matters)\n\n> Full detail moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) - load on demand.\n> Summary: full Express-vs-Standard reasoning prose; every branch is preserved in the Decision tree below.\n\n## Dependency graph (silent-failure table)\n\n| Configuration | Hard dependencies (API error without) | Silent failure mode (returns 200, does nothing) | Enables downstream |\n|---|---|---|---|\n| Express state machine | unique name; valid ASL | `.waitForTaskToken` in ASL → API rejects with definition-validation error; operators misread as IAM error and keep re-applying | — |\n| CloudWatch Logs log group | log group exists in same account + region | **log group ARN omitted at create-time → executions do not log; 5-min history rolls over and failure is invisible** | observability |\n| Log level (ALL \u002F ERROR \u002F FATAL \u002F OFF) | log group attached | **level set to OFF or FATAL only → execution-level errors invisible; operator sees empty log group** | debuggability |\n| INCLUDE_DATA \u002F EXCLUDE_DATA | log group attached | **EXCLUDE_DATA on a workflow that takes PII inputs → traces show only metadata, blocking RCA** (or inverse: INCLUDE_DATA on PII → compliance violation) | input\u002Foutput visibility |\n| IAM execution role | trust policy allows `states.\u003Cregion>.amazonaws.com` | trust policy missing service principal → `AccessDenied` on first execution; not surfaced at create-time | service integrations |\n| Sync execution (start-sync-execution) | state machine type EXPRESS | calling start-sync-execution on a Standard state machine → error; but a caller using start-execution on Express works (just async) | API Gateway \u002F direct sync |\n| EventBridge target | execution role for EventBridge to assume | **target without role → rule fires, no execution; EventBridge shows Invocations = 1, Step Functions shows Executions = 0** | scheduled recurring runs |\n| Distributed Map | state machine type EXPRESS or STANDARD; IAM allows read on ItemReader source | **Map state on Express with > 10,000-item fan-out hits 5-min cap → workflow fails mid-iteration with no progress signal** | large-scale fan-out |\n| .sync integration | supported service (Glue, Batch, ECS, SageMaker) | unsupported service in Resource ARN → API rejects; misread as syntax error | run-job-and-wait |\n| AWS SDK integration | IAM allows the underlying SDK action | **IAM allows `lambda:InvokeFunction` but the SDK integration calls `lambda:UpdateFunctionCode` → runtime AccessDenied** | direct API calls (no Lambda) |\n\n**The four silent-failure rows are the ones a baseline model\nmisses.** Missing logging, wrong log level, EXCLUDE_DATA on\ndebugging inputs, and missing EventBridge target role all return\nsuccess or wrong-shaped errors. Only Step 9 verification catches\nthe gap.\n\n## Expert heuristic: the waitForTaskToken Express block\n\n> Full detail moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) - load on demand.\n> Summary: the complete waitForTaskToken migration-trap analysis and remedies.\n\n## Expert heuristic: at-least-once idempotency\n\n> Full detail moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) - load on demand.\n> Summary: the complete at-least-once idempotency pattern with ASL example.\n\n## Expert heuristic: sync API Gateway timeout misalignment\n\n> Full detail moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) - load on demand.\n> Summary: the complete sync API Gateway timeout misalignment analysis.\n\n## Prerequisites (verify before provisioning)\n\n| Prerequisite | Why it matters | How to verify |\n|---|---|---|\n| Workflow duration fits in 5 min | Express caps at 5 min; sync API Gateway caps at 29s | estimate from longest task * longest retry; `validate-state-machine-definition` does NOT check this |\n| Workflow does NOT use `.waitForTaskToken` | Express rejects it at create-time | grep ASL for `:waitForTaskToken` |\n| IAM execution role trust policy | service principal must be `states.\u003Cregion>.amazonaws.com` | `aws iam get-role --role-name \u003CROLE>` |\n| CloudWatch Logs log group exists (recommended) | Express execution history rolls over after 5 min | `aws logs describe-log-groups --log-group-name-prefix \u002Faws\u002Fstates\u002F\u003CNAME>` |\n| Caller can assume the role (cross-account) | Cross-account callers need their own permission | caller identity policy check |\n| EventBridge rule exists (scheduled) | Scheduled Express requires an EventBridge rule + target role | `aws events describe-rule --name \u003CRULE>` |\n| AWS region supports Express | Express is available in all commercial regions | `aws stepfunctions list-state-machines --region \u003CREGION>` |\n\nIf any prerequisite is missing, output `VERDICT: PREREQUISITES_MISSING`\nand cite the specific gap.\n\n## 9-step provisioning procedure\n\n### Step 1 — Confirm Express-vs-Standard decision\n\nVerify Express is the correct type. Use this decision table:\n\n| If your workload… | Use |\n|---|---|\n| Runs > 5 minutes per execution | STANDARD |\n| Uses `.waitForTaskToken` (callbacks) | STANDARD |\n| Needs exactly-once semantics and idempotency is infeasible | STANDARD |\n| Runs \u003C 5 minutes, high-volume (>1k\u002Fday), idempotent or read-mostly | EXPRESS |\n| Triggered by EventBridge at high frequency | EXPRESS |\n| Fronted by API Gateway returning the workflow result synchronously | EXPRESS (sync) |\n| Async messaging with very high throughput | EXPRESS (async) |\n\n> Full detail moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) - load on demand.\n> Summary: the worked cost math (Standard vs Express break-even).\n\n### Step 2 — Verify workflow duration fits in the 5-minute cap\n\nSum the worst-case duration of every Task state multiplied by its\nRetry `MaxAttempts`. If the workflow includes a Distributed Map,\nsum the longest batch. If the result can exceed 5 minutes, the\nworkflow is incompatible with Express — go back to Step 1.\n\n> Full detail moved verbatim to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md) - load on demand.\n> Summary: the validate-state-machine-definition CLI (syntax-only check).\n\n**Common mistake:** assuming `validate-state-machine-definition`\nchecks the 5-min cap. It does NOT — only syntax. The cap is\nenforced at runtime; executions fail with `States.Timeout`.\n\n### Step 3 — Verify all service integrations are Express-compatible\n\n> Full detail moved verbatim to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md) - load on demand.\n> Summary: the grep command that rejects .waitForTaskToken definitions.\n\nExpress-compatible integration patterns:\n- RequestResponse (default): invoke and return immediately\n- `.sync`: invoke and wait for completion (Glue, Batch, ECS, SageMaker, Comprehend)\n- AWS SDK integrations: direct API calls without Lambda\n\nExpress-INCOMPATIBLE patterns:\n- `.waitForTaskToken`: callback pattern (unbounded wait)\n\n**Common mistake:** converting a Standard workflow that uses\n`.waitForTaskToken` for the human-approval step. Replace with a\nDynamoDB polling loop (`.sync` on a Lambda that polls approval\nstatus) or split into two workflows.\n\n### Step 4 — Define the ASL with Express-compatible patterns\n\n> Full detail moved verbatim to [references\u002Fexpress-asl-patterns.md](references\u002Fexpress-asl-patterns.md) - load on demand.\n> Summary: the complete Step 4 walkthrough with Distributed Map ASL template.\n\n### Step 5 — Create the IAM execution role with least-privilege\n\n> Full detail moved verbatim to [references\u002Fiam-and-logging-templates.md](references\u002Fiam-and-logging-templates.md) - load on demand.\n> Summary: the complete Step 5 CLI + trust\u002Fidentity policy templates.\n\n### Step 6 — Configure logging (CloudWatch Logs)\n\n> Full detail moved verbatim to [references\u002Fiam-and-logging-templates.md](references\u002Fiam-and-logging-templates.md) - load on demand.\n> Summary: the complete Step 6 logging CLI, level guidance, and pitfalls.\n\n### Step 7 — Choose sync (RequestResponse) vs async invocation\n\n| Mode | Caller | Use when |\n|---|---|---|\n| Sync | API Gateway, direct start-sync-execution | Caller needs result synchronously, workflow \u003C 29s p99 |\n| Async | EventBridge, S3, SQS, start-execution | High throughput, fire-and-forget, up to 5 min |\n\n> Full detail moved verbatim to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md) - load on demand.\n> Summary: the start-sync\u002Fstart-execution CLI and timeout-alignment warning.\n\n### Step 8 — Configure EventBridge scheduling + observability\n\n> Full detail moved verbatim to [references\u002Fscheduling-and-observability.md](references\u002Fscheduling-and-observability.md) - load on demand.\n> Summary: the complete Step 8 EventBridge rule, alarm, and X-Ray templates.\n\n### Step 9 — Verification\n\nRun every verification command and confirm each output matches the\nexpected state.\n\n> Full detail moved verbatim to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md) - load on demand.\n> Summary: the Step 9 verification CLI listing.\n\n## NEVER do these things\n\nThese anti-patterns cause silent exposure, data-plane bugs, or\ncompliance violations. Each is observed in real production incidents\n— the \"why it's wrong\" line is the post-mortem finding.\n\n1. **NEVER provision an Express workflow with `.waitForTaskToken` in\n   the ASL.** Why it's wrong: Express rejects the integration at\n   create-time (5-min cap is incompatible with unbounded callback\n   wait). The error references the line number, not the\n   incompatibility — operators loop on re-applying. Replace with\n   `.sync` for supported run-job integrations or split into a\n   Standard + Express pair.\n\n2. **NEVER deploy async Express without CloudWatch Logs enabled and\n   an `ExecutionsFailed` alarm.** Why it's wrong: async Express has\n   no caller to surface errors. The 5-min execution-history window\n   rolls over quickly; without persistent logging, failures are\n   invisible. Without an alarm, the failure may go undetected for\n   days. ALWAYS attach a log group with `level >= ERROR` and alarm\n   on `ExecutionsFailed`.\n\n3. **NEVER assume Express executions are exactly-once.** Why it's\n   wrong: Express is at-least-once. The infrastructure can restart\n   an execution on internal events; the same input can produce two\n   invocations of a side-effecting integration. Every write-path\n   integration MUST be idempotent via a key persisted BEFORE the\n   side effect.\n\n4. **NEVER front a sync Express workflow with API Gateway without\n   aligning the timeout.** Why it's wrong: API Gateway caps at 29s;\n   Express sync can run to 5 min. When p99 exceeds 29s, API Gateway\n   returns 504 while Express keeps running — the client retries,\n   producing a second execution that may double-charge if the\n   integration is non-idempotent. Set the API Gateway integration\n   timeout to 29000 ms and alarm on p99 duration > 25s.\n\n5. **NEVER set log level to OFF or FATAL on an Express workflow.**\n   Why it's wrong: OFF and FATAL produce near-empty logs, blocking\n   RCA. Use `ALL` for development and non-PII workloads; `ERROR` for\n   high-volume production. Always set `includeExecutionData=true`\n   unless the workflow processes regulated PII — and in that case,\n   redact the PII at the input, not by disabling execution data.\n\n## Output format\n\n> Full detail moved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md) - load on demand.\n> Summary: the literal output template block.\n\n## STRICT output contract\n\nThe rules below are hard constraints. Violating any one produces a\nchecklist that looks complete but contains a silent misconfiguration.\nSelf-check EVERY emitted block against these rules before returning.\n\n### Required output structure\n\nEvery response MUST be a single block using these literal labels, in\nthis order. Do NOT preface with prose, headings, or disclaimers.\n\n```text\nEXPRESS_WORKFLOW: \u003Cname>\nVERDICT: READY_TO_DEPLOY | PREREQUISITES_MISSING\nCHECKLIST:\n  [✓|✗] Express-vs-Standard decision: EXPRESS (duration \u003C 5 min, at-least-once acceptable)\n  [✓|✗] Duration budget: p99 \u003C 5 min (sync: p99 \u003C 29s)\n  [✓|✗] No .waitForTaskToken in ASL: verified\n  [✓|✗] ASL definition validated: Distributed Map \u002F .sync \u002F AWS SDK as applicable\n  [✓|✗] IAM execution role: least-privilege, service principal states.\u003Cregion>.amazonaws.com\n  [✓|✗] Logging: log-group \u002Faws\u002Fstates\u002F\u003CNAME>, level ALL|ERROR, includeExecutionData=true\n  [✓|✗] Invocation mode: sync | async (sync caller timeout aligned)\n  [✓|✗] EventBridge schedule + CloudWatch alarm: configured\n  [✓|✗] Idempotency: side-effecting integrations have idempotency key\nVERIFICATION_COMMANDS:\n  \u003Ccopy-pasteable verification commands — one per [✓] item>\n```\n\n### Decision tree: Express vs Standard\n\n```text\nExpress vs Standard — START\n  │\n  Q1: Does any single execution need to run > 5 minutes?\n  ├── YES → STANDARD (Express hard-caps at 5 min per execution)\n  └── NO  → Q2\n  │\n  Q2: Does the ASL use .waitForTaskToken (callback \u002F human-approval)?\n  ├── YES → STANDARD (Express rejects .waitForTaskToken at create-time)\n  └── NO  → Q3\n  │\n  Q3: Is exactly-once required AND idempotency is infeasible?\n  ├── YES → STANDARD (Express is at-least-once; retries can double-execute)\n  └── NO  → Q4\n  │\n  Q4: Is the workload high-volume (> 1,000 executions\u002Fday)?\n  ├── NO  → Either works; prefer STANDARD unless cost is a concern\n  └── YES → Q5\n  │\n  Q5: Can all side-effecting integrations be made idempotent?\n  ├── NO  → STANDARD (at-least-once risks duplicate writes \u002F charges)\n  └── YES → EXPRESS\n             Cost model:\n               Standard: $25.00 \u002F 1M state transitions\n               Express:  $1.00 \u002F 1M invocations + $0.025 \u002F GB-hour\n               10-state workflow, 1M runs\u002Fday:\n                 Standard = $250\u002Fday  |  Express = $1\u002Fday\n               10-state workflow, 10M runs\u002Fday:\n                 Standard = $2,500\u002Fday  |  Express = $10\u002Fday\n```\n\n### FORBIDDEN output patterns\n\n1. **NEVER emit `VERDICT: READY_TO_DEPLOY` without showing ALL 9\n   checklist items.** Every item MUST appear with a status marker:\n   `[✓]`, `[✗]`, or `[OPTIONAL]` (e.g., EventBridge schedule when\n   the workflow is not scheduled). Omitting a row implies it was\n   not evaluated.\n\n2. **NEVER mark the ASL as `[✓]` without confirming the definition\n   contains NO `.waitForTaskToken` Resource ARN suffix.** The\n   integration is silently rejected by Express at create-time; the\n   verification MUST include a `grep` or equivalent.\n\n3. **NEVER mark Logging as `[✓]` without citing the specific log\n   group name, level (ALL \u002F ERROR), and `includeExecutionData`\n   value.** A bare `[✓] Logging: configured` is non-compliant —\n   level and data-exposure flag are load-bearing. OFF and FATAL are\n   non-compliant for an Express workflow.\n\n4. **NEVER mark sync invocation as `[✓]` without confirming the\n   caller's timeout is ≤ 29s (API Gateway) or equivalent for the\n   direct caller.** Misaligned timeouts cause silent 504s while\n   Express keeps running, producing double-executions on retry.\n\n5. **NEVER mark Idempotency as `[✓]` for a workflow with side-\n   effecting integrations unless each such integration has an\n   idempotency key persisted BEFORE the side effect.** The checklist\n   MUST cite the key source (e.g.,\n   `IdempotencyKey.$: \"$$.Execution.Id\"`).\n\n6. **NEVER emit `VERDICT: PREREQUISITES_MISSING` without citing the\n   specific gap.** Each `[✗]` item MUST have a one-line reason:\n   `[✗] ASL uses .waitForTaskToken at line 42 — replace with .sync\n   or migrate to Standard`. A bare `[✗]` is non-compliant.\n\n7. **NEVER omit the cost-model comparison from the Express-vs-\n   Standard checklist row.** The row MUST cite the cost delta\n   (e.g., \"Express $1\u002FM invocations vs Standard $25\u002FM transitions\")\n   so the operator can sanity-check the type choice. A bare\n   \"EXPRESS\" without cost rationale is non-compliant.\n\n### Perfect example output — READY_TO_DEPLOY\n\nScenario: High-volume event-processing Express workflow. JSON event\nbatches land in S3; a Distributed Map fans them out to a Lambda for\nper-event processing. Async, triggered by EventBridge every 5 minutes.\nAt 2M executions\u002Fday with a 5-state workflow: Standard would cost\n~$250\u002Fday ($25\u002FM x 10M transitions); Express costs ~$2\u002Fday ($1\u002FM\nx 2M invocations). p99 execution duration = 12s.\n\n```text\nEXPRESS_WORKFLOW: event-processor-express\nVERDICT: READY_TO_DEPLOY\nCHECKLIST:\n  [✓] Express-vs-Standard decision: EXPRESS (p99 12s, idempotent;\n        cost: Express $1\u002FM invocations vs Standard $25\u002FM transitions;\n        2M runs\u002Fday x 5 states = 10M transitions -> Standard $250\u002Fday vs Express $2\u002Fday)\n  [✓] Duration budget: p99 12s \u003C 5 min (async; no sync API Gateway alignment needed)\n  [✓] No .waitForTaskToken in ASL: verified (grep -c ':waitForTaskToken' definition.json = 0)\n  [✓] ASL definition validated: Distributed Map (MaxConcurrency 1000, S3 ItemReader)\n        + Lambda Task with idempotency key (see ASL below)\n  [✓] IAM execution role: sfn-event-processor-exec, trust=states.us-east-1.amazonaws.com,\n        scoped to lambda:InvokeFunction on arn:aws:lambda:us-east-1:123456789012:function:process-event\n        + s3:GetObject on arn:aws:s3:::event-input-bucket\u002Fevents\u002F*.json\n  [✓] Logging: \u002Faws\u002Fstates\u002Fevent-processor-express, level ALL, includeExecutionData=true\n        (30-day retention; see logging CLI below)\n  [✓] Invocation mode: async (EventBridge schedule rate(5 minutes))\n  [✓] EventBridge schedule: rule event-processor-schedule, target role eventbridge-sfn-role,\n        CloudWatch alarm event-processor-failed on ExecutionsFailed >= 1\n  [✓] Idempotency: ProcessEvent Lambda checks IdempotencyKey=$$.Execution.Id against\n        DynamoDB table event-idempotency before writing; duplicate retries are no-ops\nVERIFICATION_COMMANDS:\n  aws stepfunctions describe-state-machine --state-machine-arn arn:aws:states:us-east-1:123456789012:stateMachine:event-processor-express\n  grep -c ':waitForTaskToken' definition.json\n  aws logs describe-log-groups --log-group-name-prefix \u002Faws\u002Fstates\u002Fevent-processor-express\n  aws events describe-rule --name event-processor-schedule\n  aws cloudwatch describe-alarms --alarm-names event-processor-failed\n```\n\nASL definition (Distributed Map + Lambda Task with idempotency key):\n\n```json\n{\n  \"StartAt\": \"FanOutProcess\",\n  \"States\": {\n    \"FanOutProcess\": {\n      \"Type\": \"Map\",\n      \"ItemProcessor\": {\n        \"ProcessorConfig\": { \"Mode\": \"DISTRIBUTED\" },\n        \"StartAt\": \"ProcessEvent\",\n        \"States\": {\n          \"ProcessEvent\": {\n            \"Type\": \"Task\",\n            \"Resource\": \"arn:aws:lambda:us-east-1:123456789012:function:process-event\",\n            \"Parameters\": {\n              \"IdempotencyKey.$\": \"$$.Execution.Id\",\n              \"EventPayload.$\": \"$.value\"\n            },\n            \"Retry\": [\n              { \"ErrorEquals\": [\"States.TaskFailed\"], \"MaxAttempts\": 3, \"BackoffRate\": 2 }\n            ],\n            \"End\": true\n          }\n        }\n      },\n      \"ItemReader\": {\n        \"Resource\": \"arn:aws:states:::s3:getObject\",\n        \"Parameters\": { \"Bucket\": \"event-input-bucket\", \"Key\": \"events\u002Fbatch.json\" }\n      },\n      \"MaxConcurrency\": 1000,\n      \"End\": true\n    }\n  }\n}\n```\n\nLogging configuration CLI (create log group with retention + attach\nat state machine creation):\n\n```bash\naws logs create-log-group --log-group-name \u002Faws\u002Fstates\u002Fevent-processor-express\naws logs put-retention-policy \\\n  --log-group-name \u002Faws\u002Fstates\u002Fevent-processor-express --retention-in-days 30\n\naws stepfunctions create-state-machine \\\n  --name event-processor-express \\\n  --definition file:\u002F\u002Fdefinition.json \\\n  --role-arn arn:aws:iam::123456789012:role\u002Fsfn-event-processor-exec \\\n  --type EXPRESS \\\n  --logging-configuration \\\n    level=ALL,includeExecutionData=true,\\\n    destinations='[{CloudWatchLogsLogGroup={LogGroupArn=arn:aws:logs:us-east-1:123456789012:log-group:\u002Faws\u002Fstates\u002Fevent-processor-express:*}}]'\n```\n\n### Perfect example output — PREREQUISITES_MISSING\n\n> Full detail moved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md) - load on demand.\n> Summary: the full PREREQUISITES_MISSING example with self-check list.\n\n## Recent AWS features\n\n> Full detail moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) - load on demand.\n> Summary: the full feature list (Distributed Map on Express, SDK integrations, typed ARNs, log granularity, X-Ray, IAM condition keys).\n## References (load on demand)\n\n- [references\u002Fworked-examples.md](references\u002Fworked-examples.md) - secondary example output (PREREQUISITES_MISSING) and the output-format template\n- [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md) - pre-flight validation, compatibility grep, invocation, and verification CLI listings\n- [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) - Express reasoning prose, expert heuristics, cost math, recent AWS features\n- [references\u002Fscheduling-and-observability.md](references\u002Fscheduling-and-observability.md) - EventBridge scheduling, CloudWatch alarms, X-Ray tracing templates\n- [references\u002Fexpress-asl-patterns.md](references\u002Fexpress-asl-patterns.md) - (existing) ASL patterns; now also holds the Step 4 Express ASL template\n- [references\u002Fiam-and-logging-templates.md](references\u002Fiam-and-logging-templates.md) - (existing) IAM\u002Flogging templates; now also holds Step 5-6 CLI templates\n","# Step Functions Express Workflows Deployer\n\n## What this skill does\n\nProvisions Step Functions Express Workflows and surrounding\nprimitives (CloudWatch Logs with correct level and data-exposure,\nIAM least-privilege execution role, EventBridge scheduling,\nDistributed Map configuration, idempotency guard for at-least-once\ndelivery) with production defaults. The skill walks a 9-step\nprocedure, surfaces the silent-failure modes unique to Express\n(most dangerous: `.waitForTaskToken` is rejected at create-time,\nbut operators migrating from Standard discover this only on deploy;\nlogging is NOT enabled by default, so async Express executions are\ninvisible after the 5-minute history window; the at-least-once\ndelivery model means non-idempotent Lambda handlers can double-\nexecute on retries). The single most common incident this skill\nprevents: an operator migrates a high-volume Standard workflow to\nExpress for cost savings, the migration drops CloudWatch Logs, and\nthe first failed execution is invisible — no alarm, no log, and the\n5-minute execution history has already rolled over.\n\n## Quick navigation\n\n| Section | What it covers | When to read it |\n|---|---|---|\n| **Quick reference** | Provisioning summary (9 steps), verdict thresholds | Before any operation |\n| **Activation keywords** | Phrases that route to this skill | Disambiguating routing |\n| **Reasoning framework** | Why Express is a cost + semantics decision | Choosing Express vs Standard |\n| **Dependency graph** | Which configs silently no-op without their prerequisite | Debugging \"logs are empty\" |\n| **Expert heuristic** | waitForTaskToken block; at-least-once idempotency; sync API Gateway timeouts | Pre-empt incidents |\n| **Prerequisites** | What to verify before emitting any command | Avoid PREREQUISITES_MISSING rework |\n| **9-step procedure** | The actual provisioning with copy-pasteable CLI | Executing the deploy |\n| **NEVER (top 5)** | Hard rules that prevent silent exposure \u002F data-plane bugs | Review before deploy |\n| **STRICT output contract** | Required EXPRESS_WORKFLOW \u002F VERDICT \u002F CHECKLIST \u002F VERIFICATION_COMMANDS block | Formatting the response |\n| **Recent AWS features** | Express + Distributed Map, AWS SDK direct calls | Stay current |\n\n## Quick reference — provisioning summary (9 steps)\n\n| Step | Action | Reversible? | Key risk if skipped |\n|---|---|---|---|\n| 1 | Confirm Express-vs-Standard decision (5-min cap, at-least-once, cost model) | — | wrong type = 100x cost or 5-min timeout |\n| 2 | Verify workflow duration fits in the 5-minute Express cap | Yes | sync API Gateway returns 500; async retried mid-flight |\n| 3 | Verify all service integrations are Express-compatible (NO `.waitForTaskToken`) | Yes | create-state-machine API silently rejects the definition |\n| 4 | Define the ASL with Express-compatible patterns (Distributed Map, .sync, AWS SDK) | Yes | — |\n| 5 | Create the IAM execution role with least-privilege | Yes | over-broad `states:*` on `*` |\n| 6 | Configure logging (CloudWatch Logs + level + INCLUDE_DATA\u002FEXCLUDE_DATA) | Yes | async executions invisible after 5-min history |\n| 7 | Choose sync (RequestResponse) vs async invocation mode | Yes | sync API Gateway timeout misalignment |\n| 8 | Configure EventBridge scheduling + observability (X-Ray, CloudWatch alarms) | Yes | silent failures with no alarm |\n| 9 | Verify every configuration item against actual state + emit checklist | — | silent no-ops |\n\n**Critical ordering constraints:** Express-vs-Standard decision\nfirst (every downstream choice depends on the type); duration\nbudget before ASL definition (a workflow that exceeds 5 minutes\ncannot be Express); integration compatibility before the IAM role\n(`.waitForTaskToken` rejected at create-time even with a valid\nrole); logging configuration before the first execution (without\nlogging, async Express executions are invisible after the 5-minute\nhistory rolls over); sync-vs-async choice before the caller\nintegration (API Gateway sync requires timeout alignment to ≤ 29s\nto avoid 504). Rationale and the silent-failure table are below.\n\n## Activation keywords\n\nExpress workflow, create Express state machine, Step Functions\nEXPRESS, sync express execution, start-sync-execution, async\nexpress, Express workflow logging, Step Functions CloudWatch Logs,\nINCLUDE_DATA, EXCLUDE_DATA, FATAL \u002F ERROR \u002F ALL levels, EventBridge\nStep Functions target, Distributed Map Express, Inline Map Express,\nStandard-to-Express migration, at-least-once Step Functions, Express\nidempotency, Express sync API Gateway, .sync integration Express,\nAWS SDK integration, X-Ray tracing Step Functions.\n\n## Invocation contract (hard requirement)\n\nWhen this skill is invoked with an Express Workflow provisioning\nrequest, the agent MUST respond with the checklist defined in\n§\"STRICT output contract\" using the literal all-caps labels\n`EXPRESS_WORKFLOW:`, `VERDICT:`, `CHECKLIST:`, and\n`VERIFICATION_COMMANDS:`. Do NOT preface the checklist with prose,\nheadings, or disclaimers — emit the block as the first lines of the\nresponse. This contract is what assertion-based evals and downstream\nprovisioning pipelines rely on; deviating from the literal labels\nbreaks automation silently.\n\n## Reasoning framework (why the Express decision matters)\n\n> Full detail moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) - load on demand.\n> Summary: full Express-vs-Standard reasoning prose; every branch is preserved in the Decision tree below.\n\n## Dependency graph (silent-failure table)\n\n| Configuration | Hard dependencies (API error without) | Silent failure mode (returns 200, does nothing) | Enables downstream |\n|---|---|---|---|\n| Express state machine | unique name; valid ASL | `.waitForTaskToken` in ASL → API rejects with definition-validation error; operators misread as IAM error and keep re-applying | — |\n| CloudWatch Logs log group | log group exists in same account + region | **log group ARN omitted at create-time → executions do not log; 5-min history rolls over and failure is invisible** | observability |\n| Log level (ALL \u002F ERROR \u002F FATAL \u002F OFF) | log group attached | **level set to OFF or FATAL only → execution-level errors invisible; operator sees empty log group** | debuggability |\n| INCLUDE_DATA \u002F EXCLUDE_DATA | log group attached | **EXCLUDE_DATA on a workflow that takes PII inputs → traces show only metadata, blocking RCA** (or inverse: INCLUDE_DATA on PII → compliance violation) | input\u002Foutput visibility |\n| IAM execution role | trust policy allows `states.\u003Cregion>.amazonaws.com` | trust policy missing service principal → `AccessDenied` on first execution; not surfaced at create-time | service integrations |\n| Sync execution (start-sync-execution) | state machine type EXPRESS | calling start-sync-execution on a Standard state machine → error; but a caller using start-execution on Express works (just async) | API Gateway \u002F direct sync |\n| EventBridge target | execution role for EventBridge to assume | **target without role → rule fires, no execution; EventBridge shows Invocations = 1, Step Functions shows Executions = 0** | scheduled recurring runs |\n| Distributed Map | state machine type EXPRESS or STANDARD; IAM allows read on ItemReader source | **Map state on Express with > 10,000-item fan-out hits 5-min cap → workflow fails mid-iteration with no progress signal** | large-scale fan-out |\n| .sync integration | supported service (Glue, Batch, ECS, SageMaker) | unsupported service in Resource ARN → API rejects; misread as syntax error | run-job-and-wait |\n| AWS SDK integration | IAM allows the underlying SDK action | **IAM allows `lambda:InvokeFunction` but the SDK integration calls `lambda:UpdateFunctionCode` → runtime AccessDenied** | direct API calls (no Lambda) |\n\n**The four silent-failure rows are the ones a baseline model\nmisses.** Missing logging, wrong log level, EXCLUDE_DATA on\ndebugging inputs, and missing EventBridge target role all return\nsuccess or wrong-shaped errors. Only Step 9 verification catches\nthe gap.\n\n## Expert heuristic: the waitForTaskToken Express block\n\n> Full detail moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) - load on demand.\n> Summary: the complete waitForTaskToken migration-trap analysis and remedies.\n\n## Expert heuristic: at-least-once idempotency\n\n> Full detail moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) - load on demand.\n> Summary: the complete at-least-once idempotency pattern with ASL example.\n\n## Expert heuristic: sync API Gateway timeout misalignment\n\n> Full detail moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) - load on demand.\n> Summary: the complete sync API Gateway timeout misalignment analysis.\n\n## Prerequisites (verify before provisioning)\n\n| Prerequisite | Why it matters | How to verify |\n|---|---|---|\n| Workflow duration fits in 5 min | Express caps at 5 min; sync API Gateway caps at 29s | estimate from longest task * longest retry; `validate-state-machine-definition` does NOT check this |\n| Workflow does NOT use `.waitForTaskToken` | Express rejects it at create-time | grep ASL for `:waitForTaskToken` |\n| IAM execution role trust policy | service principal must be `states.\u003Cregion>.amazonaws.com` | `aws iam get-role --role-name \u003CROLE>` |\n| CloudWatch Logs log group exists (recommended) | Express execution history rolls over after 5 min | `aws logs describe-log-groups --log-group-name-prefix \u002Faws\u002Fstates\u002F\u003CNAME>` |\n| Caller can assume the role (cross-account) | Cross-account callers need their own permission | caller identity policy check |\n| EventBridge rule exists (scheduled) | Scheduled Express requires an EventBridge rule + target role | `aws events describe-rule --name \u003CRULE>` |\n| AWS region supports Express | Express is available in all commercial regions | `aws stepfunctions list-state-machines --region \u003CREGION>` |\n\nIf any prerequisite is missing, output `VERDICT: PREREQUISITES_MISSING`\nand cite the specific gap.\n\n## 9-step provisioning procedure\n\n### Step 1 — Confirm Express-vs-Standard decision\n\nVerify Express is the correct type. Use this decision table:\n\n| If your workload… | Use |\n|---|---|\n| Runs > 5 minutes per execution | STANDARD |\n| Uses `.waitForTaskToken` (callbacks) | STANDARD |\n| Needs exactly-once semantics and idempotency is infeasible | STANDARD |\n| Runs \u003C 5 minutes, high-volume (>1k\u002Fday), idempotent or read-mostly | EXPRESS |\n| Triggered by EventBridge at high frequency | EXPRESS |\n| Fronted by API Gateway returning the workflow result synchronously | EXPRESS (sync) |\n| Async messaging with very high throughput | EXPRESS (async) |\n\n> Full detail moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) - load on demand.\n> Summary: the worked cost math (Standard vs Express break-even).\n\n### Step 2 — Verify workflow duration fits in the 5-minute cap\n\nSum the worst-case duration of every Task state multiplied by its\nRetry `MaxAttempts`. If the workflow includes a Distributed Map,\nsum the longest batch. If the result can exceed 5 minutes, the\nworkflow is incompatible with Express — go back to Step 1.\n\n> Full detail moved verbatim to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md) - load on demand.\n> Summary: the validate-state-machine-definition CLI (syntax-only check).\n\n**Common mistake:** assuming `validate-state-machine-definition`\nchecks the 5-min cap. It does NOT — only syntax. The cap is\nenforced at runtime; executions fail with `States.Timeout`.\n\n### Step 3 — Verify all service integrations are Express-compatible\n\n> Full detail moved verbatim to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md) - load on demand.\n> Summary: the grep command that rejects .waitForTaskToken definitions.\n\nExpress-compatible integration patterns:\n- RequestResponse (default): invoke and return immediately\n- `.sync`: invoke and wait for completion (Glue, Batch, ECS, SageMaker, Comprehend)\n- AWS SDK integrations: direct API calls without Lambda\n\nExpress-INCOMPATIBLE patterns:\n- `.waitForTaskToken`: callback pattern (unbounded wait)\n\n**Common mistake:** converting a Standard workflow that uses\n`.waitForTaskToken` for the human-approval step. Replace with a\nDynamoDB polling loop (`.sync` on a Lambda that polls approval\nstatus) or split into two workflows.\n\n### Step 4 — Define the ASL with Express-compatible patterns\n\n> Full detail moved verbatim to [references\u002Fexpress-asl-patterns.md](references\u002Fexpress-asl-patterns.md) - load on demand.\n> Summary: the complete Step 4 walkthrough with Distributed Map ASL template.\n\n### Step 5 — Create the IAM execution role with least-privilege\n\n> Full detail moved verbatim to [references\u002Fiam-and-logging-templates.md](references\u002Fiam-and-logging-templates.md) - load on demand.\n> Summary: the complete Step 5 CLI + trust\u002Fidentity policy templates.\n\n### Step 6 — Configure logging (CloudWatch Logs)\n\n> Full detail moved verbatim to [references\u002Fiam-and-logging-templates.md](references\u002Fiam-and-logging-templates.md) - load on demand.\n> Summary: the complete Step 6 logging CLI, level guidance, and pitfalls.\n\n### Step 7 — Choose sync (RequestResponse) vs async invocation\n\n| Mode | Caller | Use when |\n|---|---|---|\n| Sync | API Gateway, direct start-sync-execution | Caller needs result synchronously, workflow \u003C 29s p99 |\n| Async | EventBridge, S3, SQS, start-execution | High throughput, fire-and-forget, up to 5 min |\n\n> Full detail moved verbatim to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md) - load on demand.\n> Summary: the start-sync\u002Fstart-execution CLI and timeout-alignment warning.\n\n### Step 8 — Configure EventBridge scheduling + observability\n\n> Full detail moved verbatim to [references\u002Fscheduling-and-observability.md](references\u002Fscheduling-and-observability.md) - load on demand.\n> Summary: the complete Step 8 EventBridge rule, alarm, and X-Ray templates.\n\n### Step 9 — Verification\n\nRun every verification command and confirm each output matches the\nexpected state.\n\n> Full detail moved verbatim to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md) - load on demand.\n> Summary: the Step 9 verification CLI listing.\n\n## NEVER do these things\n\nThese anti-patterns cause silent exposure, data-plane bugs, or\ncompliance violations. Each is observed in real production incidents\n— the \"why it's wrong\" line is the post-mortem finding.\n\n1. **NEVER provision an Express workflow with `.waitForTaskToken` in\n   the ASL.** Why it's wrong: Express rejects the integration at\n   create-time (5-min cap is incompatible with unbounded callback\n   wait). The error references the line number, not the\n   incompatibility — operators loop on re-applying. Replace with\n   `.sync` for supported run-job integrations or split into a\n   Standard + Express pair.\n\n2. **NEVER deploy async Express without CloudWatch Logs enabled and\n   an `ExecutionsFailed` alarm.** Why it's wrong: async Express has\n   no caller to surface errors. The 5-min execution-history window\n   rolls over quickly; without persistent logging, failures are\n   invisible. Without an alarm, the failure may go undetected for\n   days. ALWAYS attach a log group with `level >= ERROR` and alarm\n   on `ExecutionsFailed`.\n\n3. **NEVER assume Express executions are exactly-once.** Why it's\n   wrong: Express is at-least-once. The infrastructure can restart\n   an execution on internal events; the same input can produce two\n   invocations of a side-effecting integration. Every write-path\n   integration MUST be idempotent via a key persisted BEFORE the\n   side effect.\n\n4. **NEVER front a sync Express workflow with API Gateway without\n   aligning the timeout.** Why it's wrong: API Gateway caps at 29s;\n   Express sync can run to 5 min. When p99 exceeds 29s, API Gateway\n   returns 504 while Express keeps running — the client retries,\n   producing a second execution that may double-charge if the\n   integration is non-idempotent. Set the API Gateway integration\n   timeout to 29000 ms and alarm on p99 duration > 25s.\n\n5. **NEVER set log level to OFF or FATAL on an Express workflow.**\n   Why it's wrong: OFF and FATAL produce near-empty logs, blocking\n   RCA. Use `ALL` for development and non-PII workloads; `ERROR` for\n   high-volume production. Always set `includeExecutionData=true`\n   unless the workflow processes regulated PII — and in that case,\n   redact the PII at the input, not by disabling execution data.\n\n## Output format\n\n> Full detail moved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md) - load on demand.\n> Summary: the literal output template block.\n\n## STRICT output contract\n\nThe rules below are hard constraints. Violating any one produces a\nchecklist that looks complete but contains a silent misconfiguration.\nSelf-check EVERY emitted block against these rules before returning.\n\n### Required output structure\n\nEvery response MUST be a single block using these literal labels, in\nthis order. Do NOT preface with prose, headings, or disclaimers.\n\n```text\nEXPRESS_WORKFLOW: \u003Cname>\nVERDICT: READY_TO_DEPLOY | PREREQUISITES_MISSING\nCHECKLIST:\n  [✓|✗] Express-vs-Standard decision: EXPRESS (duration \u003C 5 min, at-least-once acceptable)\n  [✓|✗] Duration budget: p99 \u003C 5 min (sync: p99 \u003C 29s)\n  [✓|✗] No .waitForTaskToken in ASL: verified\n  [✓|✗] ASL definition validated: Distributed Map \u002F .sync \u002F AWS SDK as applicable\n  [✓|✗] IAM execution role: least-privilege, service principal states.\u003Cregion>.amazonaws.com\n  [✓|✗] Logging: log-group \u002Faws\u002Fstates\u002F\u003CNAME>, level ALL|ERROR, includeExecutionData=true\n  [✓|✗] Invocation mode: sync | async (sync caller timeout aligned)\n  [✓|✗] EventBridge schedule + CloudWatch alarm: configured\n  [✓|✗] Idempotency: side-effecting integrations have idempotency key\nVERIFICATION_COMMANDS:\n  \u003Ccopy-pasteable verification commands — one per [✓] item>\n```\n\n### Decision tree: Express vs Standard\n\n```text\nExpress vs Standard — START\n  │\n  Q1: Does any single execution need to run > 5 minutes?\n  ├── YES → STANDARD (Express hard-caps at 5 min per execution)\n  └── NO  → Q2\n  │\n  Q2: Does the ASL use .waitForTaskToken (callback \u002F human-approval)?\n  ├── YES → STANDARD (Express rejects .waitForTaskToken at create-time)\n  └── NO  → Q3\n  │\n  Q3: Is exactly-once required AND idempotency is infeasible?\n  ├── YES → STANDARD (Express is at-least-once; retries can double-execute)\n  └── NO  → Q4\n  │\n  Q4: Is the workload high-volume (> 1,000 executions\u002Fday)?\n  ├── NO  → Either works; prefer STANDARD unless cost is a concern\n  └── YES → Q5\n  │\n  Q5: Can all side-effecting integrations be made idempotent?\n  ├── NO  → STANDARD (at-least-once risks duplicate writes \u002F charges)\n  └── YES → EXPRESS\n             Cost model:\n               Standard: $25.00 \u002F 1M state transitions\n               Express:  $1.00 \u002F 1M invocations + $0.025 \u002F GB-hour\n               10-state workflow, 1M runs\u002Fday:\n                 Standard = $250\u002Fday  |  Express = $1\u002Fday\n               10-state workflow, 10M runs\u002Fday:\n                 Standard = $2,500\u002Fday  |  Express = $10\u002Fday\n```\n\n### FORBIDDEN output patterns\n\n1. **NEVER emit `VERDICT: READY_TO_DEPLOY` without showing ALL 9\n   checklist items.** Every item MUST appear with a status marker:\n   `[✓]`, `[✗]`, or `[OPTIONAL]` (e.g., EventBridge schedule when\n   the workflow is not scheduled). Omitting a row implies it was\n   not evaluated.\n\n2. **NEVER mark the ASL as `[✓]` without confirming the definition\n   contains NO `.waitForTaskToken` Resource ARN suffix.** The\n   integration is silently rejected by Express at create-time; the\n   verification MUST include a `grep` or equivalent.\n\n3. **NEVER mark Logging as `[✓]` without citing the specific log\n   group name, level (ALL \u002F ERROR), and `includeExecutionData`\n   value.** A bare `[✓] Logging: configured` is non-compliant —\n   level and data-exposure flag are load-bearing. OFF and FATAL are\n   non-compliant for an Express workflow.\n\n4. **NEVER mark sync invocation as `[✓]` without confirming the\n   caller's timeout is ≤ 29s (API Gateway) or equivalent for the\n   direct caller.** Misaligned timeouts cause silent 504s while\n   Express keeps running, producing double-executions on retry.\n\n5. **NEVER mark Idempotency as `[✓]` for a workflow with side-\n   effecting integrations unless each such integration has an\n   idempotency key persisted BEFORE the side effect.** The checklist\n   MUST cite the key source (e.g.,\n   `IdempotencyKey.$: \"$$.Execution.Id\"`).\n\n6. **NEVER emit `VERDICT: PREREQUISITES_MISSING` without citing the\n   specific gap.** Each `[✗]` item MUST have a one-line reason:\n   `[✗] ASL uses .waitForTaskToken at line 42 — replace with .sync\n   or migrate to Standard`. A bare `[✗]` is non-compliant.\n\n7. **NEVER omit the cost-model comparison from the Express-vs-\n   Standard checklist row.** The row MUST cite the cost delta\n   (e.g., \"Express $1\u002FM invocations vs Standard $25\u002FM transitions\")\n   so the operator can sanity-check the type choice. A bare\n   \"EXPRESS\" without cost rationale is non-compliant.\n\n### Perfect example output — READY_TO_DEPLOY\n\nScenario: High-volume event-processing Express workflow. JSON event\nbatches land in S3; a Distributed Map fans them out to a Lambda for\nper-event processing. Async, triggered by EventBridge every 5 minutes.\nAt 2M executions\u002Fday with a 5-state workflow: Standard would cost\n~$250\u002Fday ($25\u002FM x 10M transitions); Express costs ~$2\u002Fday ($1\u002FM\nx 2M invocations). p99 execution duration = 12s.\n\n```text\nEXPRESS_WORKFLOW: event-processor-express\nVERDICT: READY_TO_DEPLOY\nCHECKLIST:\n  [✓] Express-vs-Standard decision: EXPRESS (p99 12s, idempotent;\n        cost: Express $1\u002FM invocations vs Standard $25\u002FM transitions;\n        2M runs\u002Fday x 5 states = 10M transitions -> Standard $250\u002Fday vs Express $2\u002Fday)\n  [✓] Duration budget: p99 12s \u003C 5 min (async; no sync API Gateway alignment needed)\n  [✓] No .waitForTaskToken in ASL: verified (grep -c ':waitForTaskToken' definition.json = 0)\n  [✓] ASL definition validated: Distributed Map (MaxConcurrency 1000, S3 ItemReader)\n        + Lambda Task with idempotency key (see ASL below)\n  [✓] IAM execution role: sfn-event-processor-exec, trust=states.us-east-1.amazonaws.com,\n        scoped to lambda:InvokeFunction on arn:aws:lambda:us-east-1:123456789012:function:process-event\n        + s3:GetObject on arn:aws:s3:::event-input-bucket\u002Fevents\u002F*.json\n  [✓] Logging: \u002Faws\u002Fstates\u002Fevent-processor-express, level ALL, includeExecutionData=true\n        (30-day retention; see logging CLI below)\n  [✓] Invocation mode: async (EventBridge schedule rate(5 minutes))\n  [✓] EventBridge schedule: rule event-processor-schedule, target role eventbridge-sfn-role,\n        CloudWatch alarm event-processor-failed on ExecutionsFailed >= 1\n  [✓] Idempotency: ProcessEvent Lambda checks IdempotencyKey=$$.Execution.Id against\n        DynamoDB table event-idempotency before writing; duplicate retries are no-ops\nVERIFICATION_COMMANDS:\n  aws stepfunctions describe-state-machine --state-machine-arn arn:aws:states:us-east-1:123456789012:stateMachine:event-processor-express\n  grep -c ':waitForTaskToken' definition.json\n  aws logs describe-log-groups --log-group-name-prefix \u002Faws\u002Fstates\u002Fevent-processor-express\n  aws events describe-rule --name event-processor-schedule\n  aws cloudwatch describe-alarms --alarm-names event-processor-failed\n```\n\nASL definition (Distributed Map + Lambda Task with idempotency key):\n\n```json\n{\n  \"StartAt\": \"FanOutProcess\",\n  \"States\": {\n    \"FanOutProcess\": {\n      \"Type\": \"Map\",\n      \"ItemProcessor\": {\n        \"ProcessorConfig\": { \"Mode\": \"DISTRIBUTED\" },\n        \"StartAt\": \"ProcessEvent\",\n        \"States\": {\n          \"ProcessEvent\": {\n            \"Type\": \"Task\",\n            \"Resource\": \"arn:aws:lambda:us-east-1:123456789012:function:process-event\",\n            \"Parameters\": {\n              \"IdempotencyKey.$\": \"$$.Execution.Id\",\n              \"EventPayload.$\": \"$.value\"\n            },\n            \"Retry\": [\n              { \"ErrorEquals\": [\"States.TaskFailed\"], \"MaxAttempts\": 3, \"BackoffRate\": 2 }\n            ],\n            \"End\": true\n          }\n        }\n      },\n      \"ItemReader\": {\n        \"Resource\": \"arn:aws:states:::s3:getObject\",\n        \"Parameters\": { \"Bucket\": \"event-input-bucket\", \"Key\": \"events\u002Fbatch.json\" }\n      },\n      \"MaxConcurrency\": 1000,\n      \"End\": true\n    }\n  }\n}\n```\n\nLogging configuration CLI (create log group with retention + attach\nat state machine creation):\n\n```bash\naws logs create-log-group --log-group-name \u002Faws\u002Fstates\u002Fevent-processor-express\naws logs put-retention-policy \\\n  --log-group-name \u002Faws\u002Fstates\u002Fevent-processor-express --retention-in-days 30\n\naws stepfunctions create-state-machine \\\n  --name event-processor-express \\\n  --definition file:\u002F\u002Fdefinition.json \\\n  --role-arn arn:aws:iam::123456789012:role\u002Fsfn-event-processor-exec \\\n  --type EXPRESS \\\n  --logging-configuration \\\n    level=ALL,includeExecutionData=true,\\\n    destinations='[{CloudWatchLogsLogGroup={LogGroupArn=arn:aws:logs:us-east-1:123456789012:log-group:\u002Faws\u002Fstates\u002Fevent-processor-express:*}}]'\n```\n\n### Perfect example output — PREREQUISITES_MISSING\n\n> Full detail moved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md) - load on demand.\n> Summary: the full PREREQUISITES_MISSING example with self-check list.\n\n## Recent AWS features\n\n> Full detail moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) - load on demand.\n> Summary: the full feature list (Distributed Map on Express, SDK integrations, typed ARNs, log granularity, X-Ray, IAM condition keys).\n## References (load on demand)\n\n- [references\u002Fworked-examples.md](references\u002Fworked-examples.md) - secondary example output (PREREQUISITES_MISSING) and the output-format template\n- [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md) - pre-flight validation, compatibility grep, invocation, and verification CLI listings\n- [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) - Express reasoning prose, expert heuristics, cost math, recent AWS features\n- [references\u002Fscheduling-and-observability.md](references\u002Fscheduling-and-observability.md) - EventBridge scheduling, CloudWatch alarms, X-Ray tracing templates\n- [references\u002Fexpress-asl-patterns.md](references\u002Fexpress-asl-patterns.md) - (existing) ASL patterns; now also holds the Step 4 Express ASL template\n- [references\u002Fiam-and-logging-templates.md](references\u002Fiam-and-logging-templates.md) - (existing) IAM\u002Flogging templates; now also holds Step 5-6 CLI templates\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":43},{"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,"lifecycle_status":40,"invocation_schema":41,"supports_pipeline":38,"activation_triggers":42},"aws, step-functions, express-workflow, state-machine, sync-execution, logging, eventbridge, deploy, app-integration","1","Jacky Chan — AWS Community Builder","aws-cloudops","AppIntegration","0.1.0","aws, step-functions, stepfunctions, express-workflow, state-machine, asl, amazon-states-language, sync-execution, requestresponse, async-execution, cloudwatch-logs, include-data, exclude-data, eventbridge, distributed-map, inline-map, sync-integration, waitfortasktoken, idempotency, at-least-once, iam-execution-role, x-ray, cloudops, deploy","deploy","high","false","capability","Provisioning a new Step Functions Express Workflow, deciding between Express and Standard (5-min cap, at-least-once semantics, per-invocation pricing), configuring sync (RequestResponse) vs async invocation, attaching a CloudWatch Logs log group with the correct level (ALL \u002F ERROR \u002F FATAL \u002F OFF) and INCLUDE_DATA \u002F EXCLUDE_DATA exposure, scheduling recurring Express executions via EventBridge, using Distributed Map or Inline Map with Express, using .sync service integrations (Glue, Batch, ECS, SageMaker), or hardening idempotency for at-least-once delivery. Do NOT invoke for Standard workflows that run >5 minutes or use .waitForTaskToken (use stepfunctions-statemachine-deployer), or for troubleshooting execution failures (use stepfunctions-execution-troubleshooter).","aws-orchestrator","true","READY_TO_DEPLOY | PREREQUISITES_MISSING","active","Input: either (a) a workflow name + ASL definition (or requirements to derive one) + sync\u002Fasync invocation mode, or (b) a Standard-to-Express migration spec (existing state machine ARN + compatibility check), or (c) an EventBridge-scheduled Express spec (schedule expression + execution role). Output: deterministic EXPRESS_WORKFLOW \u002F VERDICT \u002F CHECKLIST \u002F VERIFICATION_COMMANDS block per the STRICT output contract, where VERDICT is READY_TO_DEPLOY or PREREQUISITES_MISSING.","Express workflow, create Express state machine, Step Functions EXPRESS, sync express execution, start-sync-execution, async express, Express workflow logging, Step Functions CloudWatch Logs, INCLUDE_DATA, EXCLUDE_DATA, EventBridge Step Functions, Distributed Map Express, Standard-to-Express migration, Express idempotency","Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). Live provisioning uses AWS CLI v2 with stepfunctions (create-state-machine, update-state-machine, describe-state-machine, start-sync-execution, start-execution, validate-state-machine-definition), logs (create-log-group, put-retention-policy), events (put-rule, put-targets), iam (create-role, attach-role-policy, put-role-policy), and cloudformation \u002F terraform aws_sfn_state_machine equivalents.","main","eeace51bd5dd1db2030729d83eeab988861553aa","skills\u002Fstepfunctions-express-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":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add jhkchan\u002Faws-agent-skills --skill stepfunctions-express-deployer",{"tool":58,"command":59},"bunx","bunx skills add jhkchan\u002Faws-agent-skills --skill stepfunctions-express-deployer",{"tool":61,"command":62},"pnpm","pnpm dlx skills add jhkchan\u002Faws-agent-skills --skill stepfunctions-express-deployer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstepfunctions-express-deployer\u002FSKILL.md",true,[66,72,76,80,84,88,92,96,100,104,108,112,116,120,124,128,132,136,140,144,148],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"eval\u002Ftest-cases.yaml","REFERENCE","参考文档",6565,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstepfunctions-express-deployer\u002Feval\u002Ftest-cases.yaml",{"path":73,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":74,"sourceHtmlUrl":75},"evals\u002Fbaselines\u002Fexpress-distributed-map-logging.md",1210,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstepfunctions-express-deployer\u002Fevals\u002Fbaselines\u002Fexpress-distributed-map-logging.md",{"path":77,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":78,"sourceHtmlUrl":79},"evals\u002Fbaselines\u002Fexpress-idempotency-for-at-least-once.md",1269,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstepfunctions-express-deployer\u002Fevals\u002Fbaselines\u002Fexpress-idempotency-for-at-least-once.md",{"path":81,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":82,"sourceHtmlUrl":83},"evals\u002Fbaselines\u002Fmissing-logging-on-async.md",1085,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstepfunctions-express-deployer\u002Fevals\u002Fbaselines\u002Fmissing-logging-on-async.md",{"path":85,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":86,"sourceHtmlUrl":87},"evals\u002Fbaselines\u002Fstandard-migration-waitfortasktoken.md",1091,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstepfunctions-express-deployer\u002Fevals\u002Fbaselines\u002Fstandard-migration-waitfortasktoken.md",{"path":89,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":90,"sourceHtmlUrl":91},"evals\u002Fbaselines\u002Fsync-apigateway-timeout-alignment.md",1051,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstepfunctions-express-deployer\u002Fevals\u002Fbaselines\u002Fsync-apigateway-timeout-alignment.md",{"path":93,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":94,"sourceHtmlUrl":95},"evals\u002Feval_config.yaml",1917,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstepfunctions-express-deployer\u002Fevals\u002Feval_config.yaml",{"path":97,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":98,"sourceHtmlUrl":99},"evals\u002Fevals.json",13254,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstepfunctions-express-deployer\u002Fevals\u002Fevals.json",{"path":101,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":102,"sourceHtmlUrl":103},"evals\u002Fprompts\u002Fexpress-distributed-map-logging.md",884,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstepfunctions-express-deployer\u002Fevals\u002Fprompts\u002Fexpress-distributed-map-logging.md",{"path":105,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":106,"sourceHtmlUrl":107},"evals\u002Fprompts\u002Fexpress-idempotency-for-at-least-once.md",689,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstepfunctions-express-deployer\u002Fevals\u002Fprompts\u002Fexpress-idempotency-for-at-least-once.md",{"path":109,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":110,"sourceHtmlUrl":111},"evals\u002Fprompts\u002Fmissing-logging-on-async.md",515,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstepfunctions-express-deployer\u002Fevals\u002Fprompts\u002Fmissing-logging-on-async.md",{"path":113,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":114,"sourceHtmlUrl":115},"evals\u002Fprompts\u002Fstandard-migration-waitfortasktoken.md",621,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstepfunctions-express-deployer\u002Fevals\u002Fprompts\u002Fstandard-migration-waitfortasktoken.md",{"path":117,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":118,"sourceHtmlUrl":119},"evals\u002Fprompts\u002Fsync-apigateway-timeout-alignment.md",668,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstepfunctions-express-deployer\u002Fevals\u002Fprompts\u002Fsync-apigateway-timeout-alignment.md",{"path":121,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":122,"sourceHtmlUrl":123},"example\u002FREADME.md",7986,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstepfunctions-express-deployer\u002Fexample\u002FREADME.md",{"path":125,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":126,"sourceHtmlUrl":127},"references\u002Fadvanced-patterns.md",6026,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstepfunctions-express-deployer\u002Freferences\u002Fadvanced-patterns.md",{"path":129,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":130,"sourceHtmlUrl":131},"references\u002Fdiagnostic-commands.md",1673,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstepfunctions-express-deployer\u002Freferences\u002Fdiagnostic-commands.md",{"path":133,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":134,"sourceHtmlUrl":135},"references\u002Fexpress-asl-patterns.md",8116,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstepfunctions-express-deployer\u002Freferences\u002Fexpress-asl-patterns.md",{"path":137,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":138,"sourceHtmlUrl":139},"references\u002Fiam-and-logging-templates.md",8376,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstepfunctions-express-deployer\u002Freferences\u002Fiam-and-logging-templates.md",{"path":141,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":142,"sourceHtmlUrl":143},"references\u002Fscheduling-and-observability.md",1716,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstepfunctions-express-deployer\u002Freferences\u002Fscheduling-and-observability.md",{"path":145,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":146,"sourceHtmlUrl":147},"references\u002Fworked-examples.md",2611,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstepfunctions-express-deployer\u002Freferences\u002Fworked-examples.md",{"path":149,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":150,"sourceHtmlUrl":151},"skill.usf.yaml",4619,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstepfunctions-express-deployer\u002Fskill.usf.yaml",[153,160,167,174,181,188],{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":159,"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":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":166,"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":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":173,"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":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":178,"categories":179,"keywords":180,"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":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":187,"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":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":192,"categories":193,"keywords":194,"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",[],[]]