[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AB77PC27XRZZ3KC088QHA5":3,"skill-same:01M7AB77PC27XRZZ3KC088QHA5":146},{"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":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M7AB77PC27XRZZ3KC088QHA5","redshift-data-api-deployer",null,"Deploys AWS Redshift Data API configurations with production defaults: query execution without persistent connection (ExecuteStatement, BatchExecuteStatement, DescribeStatement, GetStatementResult), database authentication via Secrets Manager (no password in code), temporary credentials (GetClusterCredentials), statement lifecycle (SUBMITTED\u002FSTARTED\u002FFINISHED\u002FFAILED\u002FABORTED), result pagination (NextToken), abort statement (AbortStatement), ListStatements, integration with Lambda (poll DescribeStatement or EventBridge notification), cancel via StatementId, 24-hour timeout, 24-hour result expiry after completion, CloudTrail audit logging, and zero additional cost (free — standard Redshift charges apply). Emits a READY_TO_DEPLOY checklist with verification commands.. Triggers: redshift data api, execute statement, batch execute statement, describe statement, get statement result, redshift lambda query, redshift secrets manager, redshift temporary credentials, abort statement, redshift query without connection.","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\u002Fredshift-data-api-deployer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: redshift-data-api-deployer\ndescription: 'Deploys AWS Redshift Data API configurations with production defaults: query execution without persistent connection (ExecuteStatement, BatchExecuteStatement, DescribeStatement, GetStatementResult), database authentication via Secrets Manager (no password in code), temporary credentials (GetClusterCredentials), statement lifecycle (SUBMITTED\u002FSTARTED\u002FFINISHED\u002FFAILED\u002FABORTED), result pagination (NextToken), abort statement (AbortStatement), ListStatements, integration with Lambda (poll DescribeStatement or EventBridge notification), cancel via StatementId, 24-hour timeout, 24-hour result expiry after completion, CloudTrail audit logging, and zero additional cost (free — standard Redshift charges apply). Emits a READY_TO_DEPLOY checklist with verification commands.. Triggers: redshift data api, execute statement, batch execute statement, describe statement, get statement result, redshift lambda query, redshift secrets manager, redshift temporary credentials, abort statement, redshift query without connection.'\nlicense: Apache-2.0\ncompatibility: 'Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). For live deployment: AWS CLI v2 with redshift-data access. Works with Terraform aws_redshiftdata_statement resources, CloudFormation AWS::Redshift::Data, and boto3 redshift-data client.'\nmetadata:\n  domain: aws-cloudops\n  complexity: medium\n  requires_llm: 'true'\n  phase: '1'\n  supports_pipeline: 'true'\n  entry_point: 'false'\n  family: Analytics\n  task_type: deploy\n  skill_class: capability\n  lifecycle_status: active\n  verdict_shape: READY_TO_DEPLOY | PREREQUISITES_MISSING\n  version: 0.1.0\n  author: Jacky Chan — AWS Community Builder\n  tags: aws, redshift, data-api, cloudops, deploy, analytics, serverless-query, secrets-manager, cloudtrail\n  dependencies: aws-orchestrator\n  keywords: aws, redshift, data api, execute statement, batch execute, describe statement, get statement result, secrets manager, temporary credentials, cloudops, deploy, serverless query, statement lifecycle, cloudtrail\n  when_to_use: Invoke when the user wants to run Redshift queries via the Data API (no persistent connection), execute SQL from Lambda, batch-execute statements, authenticate via Secrets Manager or temporary credentials, poll statement lifecycle, paginate results, abort long-running queries, or replace JDBC\u002FODBC connection management with API calls. Do NOT invoke for Redshift cluster provisioning (use redshift-cluster- deployer), Redshift Serverless (use redshift-serverless-deployer), or query troubleshooting (use redshift-query-troubleshooter).\n---\n\n# Redshift Data API Deployer\n\nAn AWS CloudOps agent skill that deploys Redshift Data API query\nconfigurations with correct defaults. The skill walks the connection-\nfree query model, Secrets Manager vs temporary credential\nauthentication, statement lifecycle (SUBMITTED through FINISHED\u002FFAILED),\nresult pagination and 24-hour expiry, Lambda integration patterns (poll\nvs EventBridge), abort\u002Fcancel by StatementId, CloudTrail audit, and\nthe zero-cost pricing model, captures the query topology, explains why\neach default matters, and emits a READY_TO_DEPLOY checklist with\ncopy-pasteable verification commands.\n\n## Activation keywords\n\nRedshift Data API, ExecuteStatement, BatchExecuteStatement,\nDescribeStatement, GetStatementResult, Redshift Lambda query, Redshift\nSecrets Manager authentication, Redshift temporary credentials, abort\nstatement, Redshift query without connection, statement lifecycle.\n\n## STRICT output contract\n\nWhen this skill is invoked with a Redshift-Data-API deployment request\n(run queries without a persistent connection, execute SQL from Lambda,\nbatch-execute statements, or authenticate via Secrets Manager), the\nagent MUST respond with the READY_TO_DEPLOY checklist defined in the\n\"Output format\" section using the literal all-caps labels\n`DATA_API:`, `VERDICT:`, `CHECKLIST:`, and `VERIFICATION_COMMANDS:`.\nDo NOT preface the checklist with prose, headings, or disclaimers —\nemit the block as the first lines of the response. This contract is\nwhat assertion-based evals and downstream provisioning pipelines rely\non; deviating from the literal labels breaks automation silently.\n\nIf any prerequisite is missing, the verdict is `PREREQUISITES_MISSING`\nwith a specific gap citation in the checklist (marked `[✗]`), and\n`READY_TO_DEPLOY` MUST NOT also appear.\n\n## Quick navigation\n\n| Section | When to read |\n|---|---|\n| Prerequisites | Always — verify before provisioning |\n| Step 1 — Connection-free query model | Core Data API concept |\n| Step 2 — Authentication (Secrets Manager vs temp credentials) | Auth decision |\n| Step 3 — ExecuteStatement | Single-query execution |\n| Step 4 — BatchExecuteStatement | Batch SQL execution |\n| Step 5 — Statement lifecycle | SUBMITTED through FINISHED\u002FFAILED |\n| Step 6 — DescribeStatement and GetStatementResult | Polling + results |\n| Step 7 — Result pagination and 24-hour expiry | Result handling |\n| Step 8 — Lambda integration (poll vs EventBridge) | Serverless patterns |\n| Step 9 — Abort statement (cancel by StatementId) | Cancel long queries |\n| Step 10 — ListStatements and CloudTrail audit | Query governance |\n| Step 11 — Cost model and quotas | Pricing + limits |\n| Step 12 — Recent features | Latest |\n| NEVER do these things | Review before signing off |\n| Output format | The literal checklist template |\n| references\u002Fauthentication-and-secrets.md | Auth + Secrets detail |\n| references\u002Fstatement-lifecycle-and-results.md | Lifecycle + results detail |\n\n## Mindset\n\n**One-line takeaway:** The Redshift Data API lets you run SQL queries\nagainst a Redshift cluster or Redshift Serverless workgroup WITHOUT a\npersistent JDBC\u002FODBC connection. You submit a statement via API, it\nreturns a StatementId, you poll DescribeStatement for status, and when\nFINISHED you call GetStatementResult to retrieve rows. Results expire\n24 hours after completion. There is NO additional cost — standard\nRedshift charges apply.\n\n> **Moved verbatim** → [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) § \"Mindset — the three misconceptions\".\n> Load when: deciding between connection pools, result-persistence windows, or auth methods — the three misconceptions behind most Data API misdesign.\n\n## Configuration dependency graph (novel heuristic)\n\nData API configurations are NOT independent. The authentication method\ndetermines what parameters are required. The cluster\u002Fworkgroup must\nexist before queries can run. Result retrieval depends on statement\ncompletion. Use this graph to sequence deployment.\n\n| Configuration | Hard dependencies (API error without) | Silent failure \u002F immutability | Enables downstream |\n|---|---|---|---|\n| Cluster\u002Fworkgroup identifier | Redshift cluster or Serverless workgroup exists | If the cluster is paused, queries queue until resumed | query execution |\n| Authentication: Secrets Manager | Secret ARN exists; secret contains valid DB credentials | Secret must be type Redshift; DBUser\u002FDBName\u002FPassword\u002FEngineHost\u002FPort fields required | password-free auth |\n| Authentication: temp credentials | IAM principal has redshift:GetClusterCredentials | Temp creds expire after 15 min (configurable DurationSeconds) | IAM-federated auth |\n| Database name | Must match a database on the cluster | If wrong, ExecuteStatement returns \"database does not exist\" | query target |\n| DbUser (for temp creds) | Must be an existing Redshift user | AutoCreate option can create the user if set to true | user context |\n| ExecuteStatement | Cluster identifier + auth + database + SQL text | StatementId is unique per API call; SQL is case-sensitive | async query |\n| BatchExecuteStatement | Cluster + auth + database + SQL list | Each SQL in the batch runs sequentially; one failure aborts remaining | batch SQL |\n| DescribeStatement | StatementId from ExecuteStatement | Polling too frequently can hit API rate limits | status check |\n| GetStatementResult | Statement status is FINISHED | Results expire 24 hours after FINISHED; expired results are gone | row retrieval |\n| AbortStatement | Statement is SUBMITTED or STARTED | Cannot abort a FINISHED statement (no-op) | cancel long queries |\n\n**The result-expiry row is the one a baseline model misses.** Results\nare NOT permanent. The 24-hour clock starts when the statement reaches\nFINISHED — not when the statement was submitted. If a query runs for 23\nhours (within the 24-hour timeout) and finishes, results are available\nfor 24 hours AFTER that. But if a workflow submits a query, waits 25\nhours, then calls GetStatementResult, the results are already gone.\n\n**Cross-dependency gotchas:**\n- Secrets Manager auth and temp credentials auth are mutually exclusive\n  per API call. You specify EITHER SecretArn OR (DbUser with\n  temp credentials), not both.\n- BatchExecuteStatement runs SQL statements sequentially within the\n  batch. If statement 3 of 5 fails, statements 4 and 5 do NOT run.\n  The batch is NOT transactional by default.\n- DescribeStatement returns the status but NOT the rows. You must call\n  GetStatementResult separately to retrieve data rows.\n- GetStatementResult paginates with NextToken. Large result sets require\n  multiple calls.\n\n## Expert heuristic: Secrets Manager vs temporary credentials\n\nA baseline model says \"use Secrets Manager for auth.\" The correct\nheuristic recognizes that the choice depends on your security model,\ncredential rotation needs, and whether you already have a Secrets\nManager setup.\n\n```text\nAuthentication decision:\n  ├── Have a Secrets Manager secret for Redshift?\n  │     → Use SecretArn (recommended for production)\n  │     → Credentials auto-rotated via Secrets Manager rotation\n  │     → No password in application code\n  │\n  ├── Need IAM-federated access without a secret store?\n  │     → Use temporary credentials (GetClusterCredentials)\n  │     → IAM principal needs redshift:GetClusterCredentials\n  │     → Creds expire after DurationSeconds (default 900s)\n  │     → Can use AutoCreate to auto-provision DB users from IAM\n  │\n  └── Connecting from Lambda?\n        → Both work; Secrets Manager is simpler for Lambda\n        → Temp credentials avoid the Secrets Manager API call per\n          invocation (cache creds for DurationSeconds)\n        → Temp creds + AutoCreate enables IAM-based per-user access\n```\n\n**Key implication:** for Lambda workloads, temp credentials with\ncaching can reduce API calls (no Secrets Manager call per invocation).\nFor centralized credential management, Secrets Manager is better.\n\n## Expert heuristic: Lambda polling vs EventBridge notification\n\nThe Data API is asynchronous. After ExecuteStatement, you do not get\nresults immediately. Two patterns exist for getting results.\n\n```text\nPattern 1 — Lambda polling (simpler, higher cost):\n  1. Lambda calls ExecuteStatement → gets StatementId\n  2. Lambda calls DescribeStatement in a loop (with sleep)\n  3. When status = FINISHED, Lambda calls GetStatementResult\n\n  Pros: simple, self-contained, no additional services\n  Cons: Lambda is billed for the entire poll duration; sleep adds cost;\n        long-running queries may hit Lambda timeout (15 min max)\n\nPattern 2 — EventBridge notification (async, cheaper):\n  1. Lambda calls ExecuteStatement → gets StatementId\n  2. Lambda returns immediately (no polling)\n  3. EventBridge rule matches \"Redshift Data API Status Change\"\n  4. EventBridge triggers a target Lambda when status changes\n  5. Target Lambda checks if FINISHED, calls GetStatementResult\n\n  Pros: no Lambda billing for idle polling; handles long queries (>15 min)\n  Cons: more infrastructure (EventBridge rule + target Lambda); async\n        pattern is harder to reason about\n```\n\n**Key implication:** for queries under 15 minutes, Lambda polling is\nsimpler. For queries that may exceed 15 minutes (Lambda timeout), use\nEventBridge notification.\n\n## Expert heuristic: result persistence before 24-hour expiry\n\n> **Moved verbatim** → [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) § \"Result persistence before 24-hour expiry\".\n> Load when: a downstream consumer may read results later than 24 hours after FINISHED — unsafe vs safe vs UNLOAD patterns.\n\n## Prerequisites (verify before provisioning)\n\nBefore emitting deployment commands, verify these prerequisites. If any\nare missing, the verdict is **PREREQUISITES_MISSING**.\n\n| Prerequisite | Why it matters | How to verify |\n|---|---|---|\n| Redshift cluster or Serverless workgroup exists | Data API queries a cluster\u002Fworkgroup | `aws redshift describe-clusters` or `aws redshift-serverless list-workgroups` |\n| Database name confirmed | Queries target a specific database | Check `DBName` in cluster details |\n| Secrets Manager secret (if using SecretArn auth) | Provides DB credentials without passwords in code | `aws secretsmanager describe-secret --secret-id \u003Cid>` |\n| IAM permission for temp creds (if using GetClusterCredentials) | Allows generating short-lived DB credentials | Check IAM policy for `redshift:GetClusterCredentials` |\n| IAM permission for redshift-data API | Lambda\u002Fcaller needs redshift-data permissions | Check IAM policy for `redshift-data:ExecuteStatement` etc. |\n| Network access to Redshift (if not publicly accessible) | Data API connects to the cluster over the network | Verify cluster is publicly accessible OR run from within VPC |\n| SQL statement(s) prepared | ExecuteStatement requires SQL text | Prepare and validate SQL syntax |\n| Lambda function (if Lambda integration) | Lambda invokes the Data API | Confirm Lambda function exists with correct IAM role |\n\nIf any prerequisite is missing, output `VERDICT: PREREQUISITES_MISSING`\nand cite the specific gap.\n\n## Step 1 — Connection-free query model\n\nThe Data API eliminates persistent connections. Instead of:\n\n> **Moved verbatim** → [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) § \"Traditional vs Data API model\".\n> Load when: explaining the connection-free model or choosing Data API over JDBC\u002FODBC.\n\n**Key implication:** the Data API is stateless. Each API call is an\nindependent HTTP request. There is no connection pool, no idle\ntimeout, no max-connections limit. This simplifies serverless\ndeployments (Lambda, Fargate, Step Functions).\n\n## Step 2 — Authentication (Secrets Manager vs temp credentials)\n\n| Feature | Secrets Manager | Temp Credentials |\n|---|---|---|\n| Parameter | `SecretArn` | `DbUser` + IAM |\n| Password in code | No (stored in secret) | No (IAM-generated) |\n| Credential rotation | Automatic via Secrets Manager rotation | N\u002FA (short-lived, auto-generated) |\n| Expiry | Until secret is rotated | DurationSeconds (default 900s, max 3600s) |\n| AutoCreate users | No | Yes (AutoCreate: true provisions IAM-mapped DB users) |\n| Cost | Secrets Manager storage ($0.40\u002Fsecret\u002Fmonth) | No additional cost |\n| Recommended for | Production with centralized credential management | IAM-federated, per-user access |\n\n> **Moved verbatim** → [references\u002Fauthentication-and-secrets.md](references\u002Fauthentication-and-secrets.md) § \"Step 2 — auth code samples\".\n> Load when: writing the actual execute-statement commands for either auth method.\n\n## Step 3 — ExecuteStatement\n\nExecuteStatement submits a single SQL statement asynchronously.\n\n> **Moved verbatim** → [references\u002Fstatement-lifecycle-and-results.md](references\u002Fstatement-lifecycle-and-results.md) § \"Step 3 — ExecuteStatement example and parameters\".\n> Load when: composing ExecuteStatement calls or choosing WithEvent \u002F Parameters.\n\n**WithEvent:** setting `--with-event` causes the Data API to emit an\nEventBridge event when the statement status changes. This enables the\nasync Lambda pattern.\n\n## Step 4 — BatchExecuteStatement\n\nBatchExecuteStatement runs multiple SQL statements sequentially in a\nsingle API call.\n\n```bash\naws redshift-data batch-execute-statement \\\n  --cluster-identifier my-redshift-cluster \\\n  --secret-arn arn:aws:secretsmanager:us-east-1:123456789012:secret:redshift-creds-xxx \\\n  --database dev \\\n  --sqls \\\n    \"CREATE TEMP TABLE temp_sales AS SELECT * FROM sales WHERE sale_date >= '2026-01-01'\" \\\n    \"SELECT COUNT(*) FROM temp_sales\" \\\n    \"DROP TABLE temp_sales\"\n```\n\n**Key behaviors:**\n- Statements run sequentially (not parallel).\n- If statement N fails, statements N+1 through end do NOT run.\n- The batch is NOT transactional by default (no automatic rollback).\n- Returns a single StatementId for the entire batch.\n- Each statement's status can be checked via DescribeStatement.\n\n> **Moved verbatim** → [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) § \"Batch transactionality\".\n> Load when: batching SQL and needing transactional semantics — BatchExecuteStatement is NOT transactional.\n\n## Step 5 — Statement lifecycle\n\n> **Moved verbatim** → [references\u002Fstatement-lifecycle-and-results.md](references\u002Fstatement-lifecycle-and-results.md) § \"Step 5 — lifecycle states and transitions\".\n> Load when: polling lifecycle states or reading the transition table.\n\n## Step 6 — DescribeStatement and GetStatementResult\n\n> **Moved verbatim** → [references\u002Fstatement-lifecycle-and-results.md](references\u002Fstatement-lifecycle-and-results.md) § \"Step 6 — describe\u002Fresult code samples\".\n> Load when: retrieving status vs data rows.\n\n**Key distinction:** DescribeStatement gives you STATUS;\nGetStatementResult gives you DATA. You must call DescribeStatement first\nto confirm FINISHED before calling GetStatementResult.\n\n## Step 7 — Result pagination and 24-hour expiry\n\n> **Moved verbatim** → [references\u002Fstatement-lifecycle-and-results.md](references\u002Fstatement-lifecycle-and-results.md) § \"Step 7 — pagination loop and expiry\".\n> Load when: paginating large result sets or persisting results before expiry.\n\n## Step 8 — Lambda integration (poll vs EventBridge)\n\n### Pattern 1: Lambda polling\n\n> **Moved verbatim** → [references\u002Fworked-examples.md](references\u002Fworked-examples.md) § \"Pattern 1 — Lambda polling\".\n> Load when: implementing the synchronous Lambda polling pattern.\n\n### Pattern 2: EventBridge notification\n\n> **Moved verbatim** → [references\u002Fworked-examples.md](references\u002Fworked-examples.md) § \"Pattern 2 — EventBridge notification\".\n> Load when: implementing the async EventBridge pattern (WithEvent=True + target Lambda).\n\n## Step 9 — Abort statement (cancel by StatementId)\n\nAbortStatement cancels a running query by StatementId.\n\n```bash\naws redshift-data abort-statement \\\n  --statement-id \"$STATEMENT_ID\"\n```\n\n**Key behaviors:**\n- Can only abort statements in SUBMITTED or STARTED status.\n- Aborting a FINISHED statement is a no-op (returns success but does\n  nothing).\n- Abort is asynchronous — the statement moves to ABORTED after the\n  cancel propagates to Redshift.\n- Useful for long-running queries that exceed a timeout.\n\n## Step 10 — ListStatements and CloudTrail audit\n\n> **Moved verbatim** → [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) § \"ListStatements and CloudTrail audit\".\n> Load when: listing statements for governance or reasoning about CloudTrail SQL-text logging.\n\n## Step 11 — Cost model and quotas\n\n> **Moved verbatim** → [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) § \"Cost model and quotas\".\n> Load when: budgeting or checking statement timeout, result expiry, payload, concurrency, and rate quotas.\n\n## Step 12 — Recent features\n\n> **Moved verbatim** → [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) § \"Recent features (2023-2026)\".\n> Load when: using Serverless Data API, parameterized queries, ListStatements filtering, WithEvent, UNLOAD, or CloudTrail logging.\n\n## NEVER do these things\n\n1. **NEVER assume results are available beyond 24 hours after\n   FINISHED.** Results expire after 24 hours. Persist immediately if\n   needed longer. Use UNLOAD to S3 for large datasets.\n\n2. **NEVER hardcode database passwords in Lambda code.** Use Secrets\n   Manager (SecretArn) or temporary credentials (GetClusterCredentials).\n   Passwords in code are a security risk and break credential rotation.\n\n3. **NEVER assume BatchExecuteStatement is transactional.** It is NOT.\n   If statement 3 of 5 fails, statements 4-5 do NOT run, but there is no\n   automatic rollback of statements 1-2. Wrap in BEGIN\u002FCOMMIT for\n   transactional behavior.\n\n4. **NEVER call GetStatementResult before checking DescribeStatement\n   status.** GetStatementResult only works when status is FINISHED.\n   Calling it for a STARTED statement returns an error.\n\n5. **NEVER poll DescribeStatement too aggressively.** The rate limit is\n   1 call per second per statement. Polling faster causes throttling\n   errors. Use 1-5 second intervals.\n\n6. **NEVER forget the Secrets Manager IAM permission.** The Lambda\n   execution role needs `secretsmanager:GetSecretValue` on the secret\n   ARN. Without it, ExecuteStatement fails with \"access denied.\"\n\n7. **NEVER use the Data API for sub-second interactive queries.** The\n   async polling overhead (submit + poll + retrieve) adds latency. For\n   interactive workloads, use a persistent JDBC\u002FODBC connection.\n\n8. **NEVER assume AbortStatement is synchronous.** It initiates the\n   cancel but the statement moves to ABORTED asynchronously. Poll\n   DescribeStatement to confirm the ABORTED status.\n\n9. **NEVER pass SQL with user input without parameterization.** Use the\n   `Parameters` field for parameterized queries to prevent SQL injection.\n   CloudTrail logs the full SQL text, so injection attempts are visible\n   in audit logs.\n\n10. **NEVER forget the 24-hour statement timeout.** A statement auto-\n    fails after 24 hours. For ETL workloads that may exceed this, split\n    the query into smaller batches.\n\n## Output format\n\n```text\nDATA_API: \u003Ccluster-id|workgroup-name> (\u003Cauth-method: SECRET_ARN|TEMP_CREDS>)\nVERDICT: READY_TO_DEPLOY | PREREQUISITES_MISSING\nCHECKLIST:\n  [✓|✗] Cluster\u002FWorkgroup: \u003Cidentifier> (exists)\n  [✓|✗] Database: \u003Cdb-name>\n  [✓|✗] Authentication: SecretArn | TempCredentials\n  [✓|✗] Secret ARN: \u003Carn> (valid, has redshift credentials)\n  [✓|✗] IAM role: redshift-data:ExecuteStatement | DescribeStatement | GetStatementResult\n  [✓|✗] IAM role: secretsmanager:GetSecretValue (if SecretArn auth)\n  [✓|✗] IAM role: redshift:GetClusterCredentials (if temp creds auth)\n  [✓|✗] SQL: \u003Cprepared\u002Fvalidated>\n  [✓|✗] Result handling: immediate retrieval | UNLOAD to S3 | EventBridge pattern\n  [✓|✗] 24-hour result expiry: persistence plan defined\n  [✓|✗] Polling pattern: Lambda poll (interval \u003CNs>) | EventBridge async\n  [✓|✗] Abort plan: AbortStatement by StatementId\n  [✓|✗] CloudTrail audit: enabled\n  [✓|✗] Tags: \u003Ckey=value list>\nVERIFICATION_COMMANDS:\n  aws redshift-data describe-statement --id \u003Cstatement-id>\n  aws redshift-data get-statement-result --id \u003Cstatement-id>\n  aws redshift-data list-statements --status FINISHED --max-results 10\n```\n\n### Worked example — Lambda query with Secrets Manager auth\n\n```text\nDATA_API: my-redshift-cluster (SECRET_ARN)\nVERDICT: READY_TO_DEPLOY\nCHECKLIST:\n  [✓] Cluster\u002FWorkgroup: my-redshift-cluster (exists, available)\n  [✓] Database: dev\n  [✓] Authentication: SecretArn\n  [✓] Secret ARN: arn:aws:secretsmanager:us-east-1:123456789012:secret:redshift-creds-xxx\n  [✓] IAM role: redshift-data:ExecuteStatement, DescribeStatement, GetStatementResult\n  [✓] IAM role: secretsmanager:GetSecretValue on redshift-creds-xxx\n  [✓] SQL: SELECT COUNT(*) FROM sales WHERE sale_date >= '2026-01-01'\n  [✓] Result handling: immediate retrieval + write to DynamoDB\n  [✓] 24-hour result expiry: results persisted to DynamoDB within 1 minute of FINISHED\n  [✓] Polling pattern: Lambda poll (interval 2s, max 60 iterations)\n  [✓] Abort plan: AbortStatement if poll exceeds 60 iterations\n  [✓] CloudTrail audit: enabled (SQL text logged)\n  [✓] Tags: Environment=production, Workflow=sales-counter\nVERIFICATION_COMMANDS:\n  aws redshift-data describe-statement --id \u003Cstatement-id>\n  aws redshift-data get-statement-result --id \u003Cstatement-id>\n  aws redshift-data list-statements --status FINISHED --max-results 10\n```\n\n## Error handling\n\n> **Moved verbatim** → [references\u002Ferror-handling.md](references\u002Ferror-handling.md) § \"Error handling — API failures\".\n> Load when: a Data API call fails or a statement misbehaves — cluster not found, AccessDenied, expired results, stuck SUBMITTED, partial batch, Lambda poll timeout.\n\n## References (load on demand)\n\n- [references\u002Fauthentication-and-secrets.md](references\u002Fauthentication-and-secrets.md) — auth decision detail; now also holds the Step 2 Secrets Manager and temp-credential code samples moved from SKILL.md\n- [references\u002Fstatement-lifecycle-and-results.md](references\u002Fstatement-lifecycle-and-results.md) — lifecycle and results detail; now also holds the Step 3 parameter table, Step 5 lifecycle detail, Step 6 code samples, and Step 7 pagination loop moved from SKILL.md\n- [references\u002Fworked-examples.md](references\u002Fworked-examples.md) — Lambda polling and EventBridge notification full code patterns\n- [references\u002Ferror-handling.md](references\u002Ferror-handling.md) — API error deep dives (cluster not found, AccessDenied, expired results, stuck SUBMITTED, partial batch, Lambda timeout)\n- [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) — three misconceptions, result persistence, batch transactionality, CloudTrail audit, cost model and quotas, recent features\n\n## Domain\n\nAWS CloudOps \u002F Amazon Redshift Data API Serverless Query Execution.\n\n## AWS documentation\n\n- **Redshift Data API** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fredshift\u002Flatest\u002Fmgmt\u002Fdata-api.html\n- **ExecuteStatement** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fredshift\u002Flatest\u002FAPIReference\u002FAPI_ExecuteStatement.html\n- **BatchExecuteStatement** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fredshift\u002Flatest\u002FAPIReference\u002FAPI_BatchExecuteStatement.html\n- **DescribeStatement** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fredshift\u002Flatest\u002FAPIReference\u002FAPI_DescribeStatement.html\n- **GetStatementResult** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fredshift\u002Flatest\u002FAPIReference\u002FAPI_GetStatementResult.html\n- **GetClusterCredentials** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fredshift\u002Flatest\u002FAPIReference\u002FAPI_GetClusterCredentials.html\n- **Authorizing Data API** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fredshift\u002Flatest\u002Fmgmt\u002Fdata-api-auth.html\n- **Data API quotas** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fredshift\u002Flatest\u002Fmgmt\u002Fdata-api.html#data-api-limits\n- **Redshift Data API pricing** — https:\u002F\u002Faws.amazon.com\u002Fredshift\u002Fpricing\u002F\n","# Redshift Data API Deployer\n\nAn AWS CloudOps agent skill that deploys Redshift Data API query\nconfigurations with correct defaults. The skill walks the connection-\nfree query model, Secrets Manager vs temporary credential\nauthentication, statement lifecycle (SUBMITTED through FINISHED\u002FFAILED),\nresult pagination and 24-hour expiry, Lambda integration patterns (poll\nvs EventBridge), abort\u002Fcancel by StatementId, CloudTrail audit, and\nthe zero-cost pricing model, captures the query topology, explains why\neach default matters, and emits a READY_TO_DEPLOY checklist with\ncopy-pasteable verification commands.\n\n## Activation keywords\n\nRedshift Data API, ExecuteStatement, BatchExecuteStatement,\nDescribeStatement, GetStatementResult, Redshift Lambda query, Redshift\nSecrets Manager authentication, Redshift temporary credentials, abort\nstatement, Redshift query without connection, statement lifecycle.\n\n## STRICT output contract\n\nWhen this skill is invoked with a Redshift-Data-API deployment request\n(run queries without a persistent connection, execute SQL from Lambda,\nbatch-execute statements, or authenticate via Secrets Manager), the\nagent MUST respond with the READY_TO_DEPLOY checklist defined in the\n\"Output format\" section using the literal all-caps labels\n`DATA_API:`, `VERDICT:`, `CHECKLIST:`, and `VERIFICATION_COMMANDS:`.\nDo NOT preface the checklist with prose, headings, or disclaimers —\nemit the block as the first lines of the response. This contract is\nwhat assertion-based evals and downstream provisioning pipelines rely\non; deviating from the literal labels breaks automation silently.\n\nIf any prerequisite is missing, the verdict is `PREREQUISITES_MISSING`\nwith a specific gap citation in the checklist (marked `[✗]`), and\n`READY_TO_DEPLOY` MUST NOT also appear.\n\n## Quick navigation\n\n| Section | When to read |\n|---|---|\n| Prerequisites | Always — verify before provisioning |\n| Step 1 — Connection-free query model | Core Data API concept |\n| Step 2 — Authentication (Secrets Manager vs temp credentials) | Auth decision |\n| Step 3 — ExecuteStatement | Single-query execution |\n| Step 4 — BatchExecuteStatement | Batch SQL execution |\n| Step 5 — Statement lifecycle | SUBMITTED through FINISHED\u002FFAILED |\n| Step 6 — DescribeStatement and GetStatementResult | Polling + results |\n| Step 7 — Result pagination and 24-hour expiry | Result handling |\n| Step 8 — Lambda integration (poll vs EventBridge) | Serverless patterns |\n| Step 9 — Abort statement (cancel by StatementId) | Cancel long queries |\n| Step 10 — ListStatements and CloudTrail audit | Query governance |\n| Step 11 — Cost model and quotas | Pricing + limits |\n| Step 12 — Recent features | Latest |\n| NEVER do these things | Review before signing off |\n| Output format | The literal checklist template |\n| references\u002Fauthentication-and-secrets.md | Auth + Secrets detail |\n| references\u002Fstatement-lifecycle-and-results.md | Lifecycle + results detail |\n\n## Mindset\n\n**One-line takeaway:** The Redshift Data API lets you run SQL queries\nagainst a Redshift cluster or Redshift Serverless workgroup WITHOUT a\npersistent JDBC\u002FODBC connection. You submit a statement via API, it\nreturns a StatementId, you poll DescribeStatement for status, and when\nFINISHED you call GetStatementResult to retrieve rows. Results expire\n24 hours after completion. There is NO additional cost — standard\nRedshift charges apply.\n\n> **Moved verbatim** → [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) § \"Mindset — the three misconceptions\".\n> Load when: deciding between connection pools, result-persistence windows, or auth methods — the three misconceptions behind most Data API misdesign.\n\n## Configuration dependency graph (novel heuristic)\n\nData API configurations are NOT independent. The authentication method\ndetermines what parameters are required. The cluster\u002Fworkgroup must\nexist before queries can run. Result retrieval depends on statement\ncompletion. Use this graph to sequence deployment.\n\n| Configuration | Hard dependencies (API error without) | Silent failure \u002F immutability | Enables downstream |\n|---|---|---|---|\n| Cluster\u002Fworkgroup identifier | Redshift cluster or Serverless workgroup exists | If the cluster is paused, queries queue until resumed | query execution |\n| Authentication: Secrets Manager | Secret ARN exists; secret contains valid DB credentials | Secret must be type Redshift; DBUser\u002FDBName\u002FPassword\u002FEngineHost\u002FPort fields required | password-free auth |\n| Authentication: temp credentials | IAM principal has redshift:GetClusterCredentials | Temp creds expire after 15 min (configurable DurationSeconds) | IAM-federated auth |\n| Database name | Must match a database on the cluster | If wrong, ExecuteStatement returns \"database does not exist\" | query target |\n| DbUser (for temp creds) | Must be an existing Redshift user | AutoCreate option can create the user if set to true | user context |\n| ExecuteStatement | Cluster identifier + auth + database + SQL text | StatementId is unique per API call; SQL is case-sensitive | async query |\n| BatchExecuteStatement | Cluster + auth + database + SQL list | Each SQL in the batch runs sequentially; one failure aborts remaining | batch SQL |\n| DescribeStatement | StatementId from ExecuteStatement | Polling too frequently can hit API rate limits | status check |\n| GetStatementResult | Statement status is FINISHED | Results expire 24 hours after FINISHED; expired results are gone | row retrieval |\n| AbortStatement | Statement is SUBMITTED or STARTED | Cannot abort a FINISHED statement (no-op) | cancel long queries |\n\n**The result-expiry row is the one a baseline model misses.** Results\nare NOT permanent. The 24-hour clock starts when the statement reaches\nFINISHED — not when the statement was submitted. If a query runs for 23\nhours (within the 24-hour timeout) and finishes, results are available\nfor 24 hours AFTER that. But if a workflow submits a query, waits 25\nhours, then calls GetStatementResult, the results are already gone.\n\n**Cross-dependency gotchas:**\n- Secrets Manager auth and temp credentials auth are mutually exclusive\n  per API call. You specify EITHER SecretArn OR (DbUser with\n  temp credentials), not both.\n- BatchExecuteStatement runs SQL statements sequentially within the\n  batch. If statement 3 of 5 fails, statements 4 and 5 do NOT run.\n  The batch is NOT transactional by default.\n- DescribeStatement returns the status but NOT the rows. You must call\n  GetStatementResult separately to retrieve data rows.\n- GetStatementResult paginates with NextToken. Large result sets require\n  multiple calls.\n\n## Expert heuristic: Secrets Manager vs temporary credentials\n\nA baseline model says \"use Secrets Manager for auth.\" The correct\nheuristic recognizes that the choice depends on your security model,\ncredential rotation needs, and whether you already have a Secrets\nManager setup.\n\n```text\nAuthentication decision:\n  ├── Have a Secrets Manager secret for Redshift?\n  │     → Use SecretArn (recommended for production)\n  │     → Credentials auto-rotated via Secrets Manager rotation\n  │     → No password in application code\n  │\n  ├── Need IAM-federated access without a secret store?\n  │     → Use temporary credentials (GetClusterCredentials)\n  │     → IAM principal needs redshift:GetClusterCredentials\n  │     → Creds expire after DurationSeconds (default 900s)\n  │     → Can use AutoCreate to auto-provision DB users from IAM\n  │\n  └── Connecting from Lambda?\n        → Both work; Secrets Manager is simpler for Lambda\n        → Temp credentials avoid the Secrets Manager API call per\n          invocation (cache creds for DurationSeconds)\n        → Temp creds + AutoCreate enables IAM-based per-user access\n```\n\n**Key implication:** for Lambda workloads, temp credentials with\ncaching can reduce API calls (no Secrets Manager call per invocation).\nFor centralized credential management, Secrets Manager is better.\n\n## Expert heuristic: Lambda polling vs EventBridge notification\n\nThe Data API is asynchronous. After ExecuteStatement, you do not get\nresults immediately. Two patterns exist for getting results.\n\n```text\nPattern 1 — Lambda polling (simpler, higher cost):\n  1. Lambda calls ExecuteStatement → gets StatementId\n  2. Lambda calls DescribeStatement in a loop (with sleep)\n  3. When status = FINISHED, Lambda calls GetStatementResult\n\n  Pros: simple, self-contained, no additional services\n  Cons: Lambda is billed for the entire poll duration; sleep adds cost;\n        long-running queries may hit Lambda timeout (15 min max)\n\nPattern 2 — EventBridge notification (async, cheaper):\n  1. Lambda calls ExecuteStatement → gets StatementId\n  2. Lambda returns immediately (no polling)\n  3. EventBridge rule matches \"Redshift Data API Status Change\"\n  4. EventBridge triggers a target Lambda when status changes\n  5. Target Lambda checks if FINISHED, calls GetStatementResult\n\n  Pros: no Lambda billing for idle polling; handles long queries (>15 min)\n  Cons: more infrastructure (EventBridge rule + target Lambda); async\n        pattern is harder to reason about\n```\n\n**Key implication:** for queries under 15 minutes, Lambda polling is\nsimpler. For queries that may exceed 15 minutes (Lambda timeout), use\nEventBridge notification.\n\n## Expert heuristic: result persistence before 24-hour expiry\n\n> **Moved verbatim** → [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) § \"Result persistence before 24-hour expiry\".\n> Load when: a downstream consumer may read results later than 24 hours after FINISHED — unsafe vs safe vs UNLOAD patterns.\n\n## Prerequisites (verify before provisioning)\n\nBefore emitting deployment commands, verify these prerequisites. If any\nare missing, the verdict is **PREREQUISITES_MISSING**.\n\n| Prerequisite | Why it matters | How to verify |\n|---|---|---|\n| Redshift cluster or Serverless workgroup exists | Data API queries a cluster\u002Fworkgroup | `aws redshift describe-clusters` or `aws redshift-serverless list-workgroups` |\n| Database name confirmed | Queries target a specific database | Check `DBName` in cluster details |\n| Secrets Manager secret (if using SecretArn auth) | Provides DB credentials without passwords in code | `aws secretsmanager describe-secret --secret-id \u003Cid>` |\n| IAM permission for temp creds (if using GetClusterCredentials) | Allows generating short-lived DB credentials | Check IAM policy for `redshift:GetClusterCredentials` |\n| IAM permission for redshift-data API | Lambda\u002Fcaller needs redshift-data permissions | Check IAM policy for `redshift-data:ExecuteStatement` etc. |\n| Network access to Redshift (if not publicly accessible) | Data API connects to the cluster over the network | Verify cluster is publicly accessible OR run from within VPC |\n| SQL statement(s) prepared | ExecuteStatement requires SQL text | Prepare and validate SQL syntax |\n| Lambda function (if Lambda integration) | Lambda invokes the Data API | Confirm Lambda function exists with correct IAM role |\n\nIf any prerequisite is missing, output `VERDICT: PREREQUISITES_MISSING`\nand cite the specific gap.\n\n## Step 1 — Connection-free query model\n\nThe Data API eliminates persistent connections. Instead of:\n\n> **Moved verbatim** → [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) § \"Traditional vs Data API model\".\n> Load when: explaining the connection-free model or choosing Data API over JDBC\u002FODBC.\n\n**Key implication:** the Data API is stateless. Each API call is an\nindependent HTTP request. There is no connection pool, no idle\ntimeout, no max-connections limit. This simplifies serverless\ndeployments (Lambda, Fargate, Step Functions).\n\n## Step 2 — Authentication (Secrets Manager vs temp credentials)\n\n| Feature | Secrets Manager | Temp Credentials |\n|---|---|---|\n| Parameter | `SecretArn` | `DbUser` + IAM |\n| Password in code | No (stored in secret) | No (IAM-generated) |\n| Credential rotation | Automatic via Secrets Manager rotation | N\u002FA (short-lived, auto-generated) |\n| Expiry | Until secret is rotated | DurationSeconds (default 900s, max 3600s) |\n| AutoCreate users | No | Yes (AutoCreate: true provisions IAM-mapped DB users) |\n| Cost | Secrets Manager storage ($0.40\u002Fsecret\u002Fmonth) | No additional cost |\n| Recommended for | Production with centralized credential management | IAM-federated, per-user access |\n\n> **Moved verbatim** → [references\u002Fauthentication-and-secrets.md](references\u002Fauthentication-and-secrets.md) § \"Step 2 — auth code samples\".\n> Load when: writing the actual execute-statement commands for either auth method.\n\n## Step 3 — ExecuteStatement\n\nExecuteStatement submits a single SQL statement asynchronously.\n\n> **Moved verbatim** → [references\u002Fstatement-lifecycle-and-results.md](references\u002Fstatement-lifecycle-and-results.md) § \"Step 3 — ExecuteStatement example and parameters\".\n> Load when: composing ExecuteStatement calls or choosing WithEvent \u002F Parameters.\n\n**WithEvent:** setting `--with-event` causes the Data API to emit an\nEventBridge event when the statement status changes. This enables the\nasync Lambda pattern.\n\n## Step 4 — BatchExecuteStatement\n\nBatchExecuteStatement runs multiple SQL statements sequentially in a\nsingle API call.\n\n```bash\naws redshift-data batch-execute-statement \\\n  --cluster-identifier my-redshift-cluster \\\n  --secret-arn arn:aws:secretsmanager:us-east-1:123456789012:secret:redshift-creds-xxx \\\n  --database dev \\\n  --sqls \\\n    \"CREATE TEMP TABLE temp_sales AS SELECT * FROM sales WHERE sale_date >= '2026-01-01'\" \\\n    \"SELECT COUNT(*) FROM temp_sales\" \\\n    \"DROP TABLE temp_sales\"\n```\n\n**Key behaviors:**\n- Statements run sequentially (not parallel).\n- If statement N fails, statements N+1 through end do NOT run.\n- The batch is NOT transactional by default (no automatic rollback).\n- Returns a single StatementId for the entire batch.\n- Each statement's status can be checked via DescribeStatement.\n\n> **Moved verbatim** → [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) § \"Batch transactionality\".\n> Load when: batching SQL and needing transactional semantics — BatchExecuteStatement is NOT transactional.\n\n## Step 5 — Statement lifecycle\n\n> **Moved verbatim** → [references\u002Fstatement-lifecycle-and-results.md](references\u002Fstatement-lifecycle-and-results.md) § \"Step 5 — lifecycle states and transitions\".\n> Load when: polling lifecycle states or reading the transition table.\n\n## Step 6 — DescribeStatement and GetStatementResult\n\n> **Moved verbatim** → [references\u002Fstatement-lifecycle-and-results.md](references\u002Fstatement-lifecycle-and-results.md) § \"Step 6 — describe\u002Fresult code samples\".\n> Load when: retrieving status vs data rows.\n\n**Key distinction:** DescribeStatement gives you STATUS;\nGetStatementResult gives you DATA. You must call DescribeStatement first\nto confirm FINISHED before calling GetStatementResult.\n\n## Step 7 — Result pagination and 24-hour expiry\n\n> **Moved verbatim** → [references\u002Fstatement-lifecycle-and-results.md](references\u002Fstatement-lifecycle-and-results.md) § \"Step 7 — pagination loop and expiry\".\n> Load when: paginating large result sets or persisting results before expiry.\n\n## Step 8 — Lambda integration (poll vs EventBridge)\n\n### Pattern 1: Lambda polling\n\n> **Moved verbatim** → [references\u002Fworked-examples.md](references\u002Fworked-examples.md) § \"Pattern 1 — Lambda polling\".\n> Load when: implementing the synchronous Lambda polling pattern.\n\n### Pattern 2: EventBridge notification\n\n> **Moved verbatim** → [references\u002Fworked-examples.md](references\u002Fworked-examples.md) § \"Pattern 2 — EventBridge notification\".\n> Load when: implementing the async EventBridge pattern (WithEvent=True + target Lambda).\n\n## Step 9 — Abort statement (cancel by StatementId)\n\nAbortStatement cancels a running query by StatementId.\n\n```bash\naws redshift-data abort-statement \\\n  --statement-id \"$STATEMENT_ID\"\n```\n\n**Key behaviors:**\n- Can only abort statements in SUBMITTED or STARTED status.\n- Aborting a FINISHED statement is a no-op (returns success but does\n  nothing).\n- Abort is asynchronous — the statement moves to ABORTED after the\n  cancel propagates to Redshift.\n- Useful for long-running queries that exceed a timeout.\n\n## Step 10 — ListStatements and CloudTrail audit\n\n> **Moved verbatim** → [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) § \"ListStatements and CloudTrail audit\".\n> Load when: listing statements for governance or reasoning about CloudTrail SQL-text logging.\n\n## Step 11 — Cost model and quotas\n\n> **Moved verbatim** → [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) § \"Cost model and quotas\".\n> Load when: budgeting or checking statement timeout, result expiry, payload, concurrency, and rate quotas.\n\n## Step 12 — Recent features\n\n> **Moved verbatim** → [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) § \"Recent features (2023-2026)\".\n> Load when: using Serverless Data API, parameterized queries, ListStatements filtering, WithEvent, UNLOAD, or CloudTrail logging.\n\n## NEVER do these things\n\n1. **NEVER assume results are available beyond 24 hours after\n   FINISHED.** Results expire after 24 hours. Persist immediately if\n   needed longer. Use UNLOAD to S3 for large datasets.\n\n2. **NEVER hardcode database passwords in Lambda code.** Use Secrets\n   Manager (SecretArn) or temporary credentials (GetClusterCredentials).\n   Passwords in code are a security risk and break credential rotation.\n\n3. **NEVER assume BatchExecuteStatement is transactional.** It is NOT.\n   If statement 3 of 5 fails, statements 4-5 do NOT run, but there is no\n   automatic rollback of statements 1-2. Wrap in BEGIN\u002FCOMMIT for\n   transactional behavior.\n\n4. **NEVER call GetStatementResult before checking DescribeStatement\n   status.** GetStatementResult only works when status is FINISHED.\n   Calling it for a STARTED statement returns an error.\n\n5. **NEVER poll DescribeStatement too aggressively.** The rate limit is\n   1 call per second per statement. Polling faster causes throttling\n   errors. Use 1-5 second intervals.\n\n6. **NEVER forget the Secrets Manager IAM permission.** The Lambda\n   execution role needs `secretsmanager:GetSecretValue` on the secret\n   ARN. Without it, ExecuteStatement fails with \"access denied.\"\n\n7. **NEVER use the Data API for sub-second interactive queries.** The\n   async polling overhead (submit + poll + retrieve) adds latency. For\n   interactive workloads, use a persistent JDBC\u002FODBC connection.\n\n8. **NEVER assume AbortStatement is synchronous.** It initiates the\n   cancel but the statement moves to ABORTED asynchronously. Poll\n   DescribeStatement to confirm the ABORTED status.\n\n9. **NEVER pass SQL with user input without parameterization.** Use the\n   `Parameters` field for parameterized queries to prevent SQL injection.\n   CloudTrail logs the full SQL text, so injection attempts are visible\n   in audit logs.\n\n10. **NEVER forget the 24-hour statement timeout.** A statement auto-\n    fails after 24 hours. For ETL workloads that may exceed this, split\n    the query into smaller batches.\n\n## Output format\n\n```text\nDATA_API: \u003Ccluster-id|workgroup-name> (\u003Cauth-method: SECRET_ARN|TEMP_CREDS>)\nVERDICT: READY_TO_DEPLOY | PREREQUISITES_MISSING\nCHECKLIST:\n  [✓|✗] Cluster\u002FWorkgroup: \u003Cidentifier> (exists)\n  [✓|✗] Database: \u003Cdb-name>\n  [✓|✗] Authentication: SecretArn | TempCredentials\n  [✓|✗] Secret ARN: \u003Carn> (valid, has redshift credentials)\n  [✓|✗] IAM role: redshift-data:ExecuteStatement | DescribeStatement | GetStatementResult\n  [✓|✗] IAM role: secretsmanager:GetSecretValue (if SecretArn auth)\n  [✓|✗] IAM role: redshift:GetClusterCredentials (if temp creds auth)\n  [✓|✗] SQL: \u003Cprepared\u002Fvalidated>\n  [✓|✗] Result handling: immediate retrieval | UNLOAD to S3 | EventBridge pattern\n  [✓|✗] 24-hour result expiry: persistence plan defined\n  [✓|✗] Polling pattern: Lambda poll (interval \u003CNs>) | EventBridge async\n  [✓|✗] Abort plan: AbortStatement by StatementId\n  [✓|✗] CloudTrail audit: enabled\n  [✓|✗] Tags: \u003Ckey=value list>\nVERIFICATION_COMMANDS:\n  aws redshift-data describe-statement --id \u003Cstatement-id>\n  aws redshift-data get-statement-result --id \u003Cstatement-id>\n  aws redshift-data list-statements --status FINISHED --max-results 10\n```\n\n### Worked example — Lambda query with Secrets Manager auth\n\n```text\nDATA_API: my-redshift-cluster (SECRET_ARN)\nVERDICT: READY_TO_DEPLOY\nCHECKLIST:\n  [✓] Cluster\u002FWorkgroup: my-redshift-cluster (exists, available)\n  [✓] Database: dev\n  [✓] Authentication: SecretArn\n  [✓] Secret ARN: arn:aws:secretsmanager:us-east-1:123456789012:secret:redshift-creds-xxx\n  [✓] IAM role: redshift-data:ExecuteStatement, DescribeStatement, GetStatementResult\n  [✓] IAM role: secretsmanager:GetSecretValue on redshift-creds-xxx\n  [✓] SQL: SELECT COUNT(*) FROM sales WHERE sale_date >= '2026-01-01'\n  [✓] Result handling: immediate retrieval + write to DynamoDB\n  [✓] 24-hour result expiry: results persisted to DynamoDB within 1 minute of FINISHED\n  [✓] Polling pattern: Lambda poll (interval 2s, max 60 iterations)\n  [✓] Abort plan: AbortStatement if poll exceeds 60 iterations\n  [✓] CloudTrail audit: enabled (SQL text logged)\n  [✓] Tags: Environment=production, Workflow=sales-counter\nVERIFICATION_COMMANDS:\n  aws redshift-data describe-statement --id \u003Cstatement-id>\n  aws redshift-data get-statement-result --id \u003Cstatement-id>\n  aws redshift-data list-statements --status FINISHED --max-results 10\n```\n\n## Error handling\n\n> **Moved verbatim** → [references\u002Ferror-handling.md](references\u002Ferror-handling.md) § \"Error handling — API failures\".\n> Load when: a Data API call fails or a statement misbehaves — cluster not found, AccessDenied, expired results, stuck SUBMITTED, partial batch, Lambda poll timeout.\n\n## References (load on demand)\n\n- [references\u002Fauthentication-and-secrets.md](references\u002Fauthentication-and-secrets.md) — auth decision detail; now also holds the Step 2 Secrets Manager and temp-credential code samples moved from SKILL.md\n- [references\u002Fstatement-lifecycle-and-results.md](references\u002Fstatement-lifecycle-and-results.md) — lifecycle and results detail; now also holds the Step 3 parameter table, Step 5 lifecycle detail, Step 6 code samples, and Step 7 pagination loop moved from SKILL.md\n- [references\u002Fworked-examples.md](references\u002Fworked-examples.md) — Lambda polling and EventBridge notification full code patterns\n- [references\u002Ferror-handling.md](references\u002Ferror-handling.md) — API error deep dives (cluster not found, AccessDenied, expired results, stuck SUBMITTED, partial batch, Lambda timeout)\n- [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) — three misconceptions, result persistence, batch transactionality, CloudTrail audit, cost model and quotas, recent features\n\n## Domain\n\nAWS CloudOps \u002F Amazon Redshift Data API Serverless Query Execution.\n\n## AWS documentation\n\n- **Redshift Data API** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fredshift\u002Flatest\u002Fmgmt\u002Fdata-api.html\n- **ExecuteStatement** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fredshift\u002Flatest\u002FAPIReference\u002FAPI_ExecuteStatement.html\n- **BatchExecuteStatement** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fredshift\u002Flatest\u002FAPIReference\u002FAPI_BatchExecuteStatement.html\n- **DescribeStatement** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fredshift\u002Flatest\u002FAPIReference\u002FAPI_DescribeStatement.html\n- **GetStatementResult** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fredshift\u002Flatest\u002FAPIReference\u002FAPI_GetStatementResult.html\n- **GetClusterCredentials** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fredshift\u002Flatest\u002FAPIReference\u002FAPI_GetClusterCredentials.html\n- **Authorizing Data API** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fredshift\u002Flatest\u002Fmgmt\u002Fdata-api-auth.html\n- **Data API quotas** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fredshift\u002Flatest\u002Fmgmt\u002Fdata-api.html#data-api-limits\n- **Redshift Data API pricing** — https:\u002F\u002Faws.amazon.com\u002Fredshift\u002Fpricing\u002F\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":41},{"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,"supports_pipeline":38},"aws, redshift, data-api, cloudops, deploy, analytics, serverless-query, secrets-manager, cloudtrail","1","Jacky Chan — AWS Community Builder","aws-cloudops","Analytics","0.1.0","aws, redshift, data api, execute statement, batch execute, describe statement, get statement result, secrets manager, temporary credentials, cloudops, deploy, serverless query, statement lifecycle, cloudtrail","deploy","medium","false","capability","Invoke when the user wants to run Redshift queries via the Data API (no persistent connection), execute SQL from Lambda, batch-execute statements, authenticate via Secrets Manager or temporary credentials, poll statement lifecycle, paginate results, abort long-running queries, or replace JDBC\u002FODBC connection management with API calls. Do NOT invoke for Redshift cluster provisioning (use redshift-cluster- deployer), Redshift Serverless (use redshift-serverless-deployer), or query troubleshooting (use redshift-query-troubleshooter).","aws-orchestrator","true","READY_TO_DEPLOY | PREREQUISITES_MISSING","active","Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). For live deployment: AWS CLI v2 with redshift-data access. Works with Terraform aws_redshiftdata_statement resources, CloudFormation AWS::Redshift::Data, and boto3 redshift-data client.","main","eeace51bd5dd1db2030729d83eeab988861553aa","skills\u002Fredshift-data-api-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":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add jhkchan\u002Faws-agent-skills --skill redshift-data-api-deployer",{"tool":56,"command":57},"bunx","bunx skills add jhkchan\u002Faws-agent-skills --skill redshift-data-api-deployer",{"tool":59,"command":60},"pnpm","pnpm dlx skills add jhkchan\u002Faws-agent-skills --skill redshift-data-api-deployer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fredshift-data-api-deployer\u002FSKILL.md",true,[64,70,74,78,82,86,90,94,98,102,106,110,114,118,122,126,130,134,138,142],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"eval\u002Ftest-cases.yaml","REFERENCE","参考文档",6256,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fredshift-data-api-deployer\u002Feval\u002Ftest-cases.yaml",{"path":71,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":72,"sourceHtmlUrl":73},"evals\u002Fbaselines\u002Flambda-poll-lifecycle.md",1039,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fredshift-data-api-deployer\u002Fevals\u002Fbaselines\u002Flambda-poll-lifecycle.md",{"path":75,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":76,"sourceHtmlUrl":77},"evals\u002Fbaselines\u002Fmissing-secret-access.md",838,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fredshift-data-api-deployer\u002Fevals\u002Fbaselines\u002Fmissing-secret-access.md",{"path":79,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":80,"sourceHtmlUrl":81},"evals\u002Fbaselines\u002Fsecrets-manager-auth-query.md",959,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fredshift-data-api-deployer\u002Fevals\u002Fbaselines\u002Fsecrets-manager-auth-query.md",{"path":83,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":84,"sourceHtmlUrl":85},"evals\u002Fbaselines\u002Fstatement-result-pagination.md",869,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fredshift-data-api-deployer\u002Fevals\u002Fbaselines\u002Fstatement-result-pagination.md",{"path":87,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":88,"sourceHtmlUrl":89},"evals\u002Fbaselines\u002Ftemp-credentials-batch-execute.md",825,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fredshift-data-api-deployer\u002Fevals\u002Fbaselines\u002Ftemp-credentials-batch-execute.md",{"path":91,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":92,"sourceHtmlUrl":93},"evals\u002Feval_config.yaml",1798,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fredshift-data-api-deployer\u002Fevals\u002Feval_config.yaml",{"path":95,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":96,"sourceHtmlUrl":97},"evals\u002Fevals.json",9663,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fredshift-data-api-deployer\u002Fevals\u002Fevals.json",{"path":99,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":100,"sourceHtmlUrl":101},"evals\u002Fprompts\u002Flambda-poll-lifecycle.md",665,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fredshift-data-api-deployer\u002Fevals\u002Fprompts\u002Flambda-poll-lifecycle.md",{"path":103,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":104,"sourceHtmlUrl":105},"evals\u002Fprompts\u002Fmissing-secret-access.md",564,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fredshift-data-api-deployer\u002Fevals\u002Fprompts\u002Fmissing-secret-access.md",{"path":107,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":108,"sourceHtmlUrl":109},"evals\u002Fprompts\u002Fsecrets-manager-auth-query.md",686,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fredshift-data-api-deployer\u002Fevals\u002Fprompts\u002Fsecrets-manager-auth-query.md",{"path":111,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":112,"sourceHtmlUrl":113},"evals\u002Fprompts\u002Fstatement-result-pagination.md",659,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fredshift-data-api-deployer\u002Fevals\u002Fprompts\u002Fstatement-result-pagination.md",{"path":115,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":116,"sourceHtmlUrl":117},"evals\u002Fprompts\u002Ftemp-credentials-batch-execute.md",614,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fredshift-data-api-deployer\u002Fevals\u002Fprompts\u002Ftemp-credentials-batch-execute.md",{"path":119,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":120,"sourceHtmlUrl":121},"examples\u002FREADME.md",7337,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fredshift-data-api-deployer\u002Fexamples\u002FREADME.md",{"path":123,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":124,"sourceHtmlUrl":125},"references\u002Fadvanced-patterns.md",6693,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fredshift-data-api-deployer\u002Freferences\u002Fadvanced-patterns.md",{"path":127,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":128,"sourceHtmlUrl":129},"references\u002Fauthentication-and-secrets.md",8714,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fredshift-data-api-deployer\u002Freferences\u002Fauthentication-and-secrets.md",{"path":131,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":132,"sourceHtmlUrl":133},"references\u002Ferror-handling.md",1259,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fredshift-data-api-deployer\u002Freferences\u002Ferror-handling.md",{"path":135,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":136,"sourceHtmlUrl":137},"references\u002Fstatement-lifecycle-and-results.md",14685,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fredshift-data-api-deployer\u002Freferences\u002Fstatement-lifecycle-and-results.md",{"path":139,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":140,"sourceHtmlUrl":141},"references\u002Fworked-examples.md",2014,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fredshift-data-api-deployer\u002Freferences\u002Fworked-examples.md",{"path":143,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":144,"sourceHtmlUrl":145},"skill.usf.yaml",4645,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fredshift-data-api-deployer\u002Fskill.usf.yaml",[147,154,161,168,175,182],{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":153,"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":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":160,"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":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":167,"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":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":174,"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":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":181,"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":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":188,"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",[],[]]