[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ACS81WS6XKN2QAZMAYMF7F":3,"skill-same:01M7ACS81WS6XKN2QAZMAYMF7F":142},{"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},"01M7ACS81WS6XKN2QAZMAYMF7F","sqs-fifo-deployer",null,"Provisions Amazon SQS FIFO queues with production defaults: FIFO queue attributes (FifoQueue=true, ContentBasedDeduplication, DeduplicationScope, ThroughputLimit mode), message group ID for ordering, deduplication (content-based vs explicit), high-throughput FIFO mode, DLQ for FIFO, visibility timeout tuning, SSE-KMS encryption, access policy, redrive policy, and cross-account delivery. Emits a READY_TO_DEPLOY checklist with verification commands. Use when creating an SQS FIFO queue, setting up message group ordering, configuring deduplication, enabling high-throughput FIFO, attaching a DLQ, tuning visibility timeout, or configuring cross-account delivery. Triggers: create sqs fifo queue, fifo queue deduplication, sqs message group id, high throughput fifo, sqs dlq redrive, sqs visibility timeout, sqs sse kms, sqs fifo cross account.","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\u002Fsqs-fifo-deployer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: sqs-fifo-deployer\ndescription: 'Provisions Amazon SQS FIFO queues with production defaults: FIFO queue attributes (FifoQueue=true, ContentBasedDeduplication, DeduplicationScope, ThroughputLimit mode), message group ID for ordering, deduplication (content-based vs explicit), high-throughput FIFO mode, DLQ for FIFO, visibility timeout tuning, SSE-KMS encryption, access policy, redrive policy, and cross-account delivery. Emits a READY_TO_DEPLOY checklist with verification commands. Use when creating an SQS FIFO queue, setting up message group ordering, configuring deduplication, enabling high-throughput FIFO, attaching a DLQ, tuning visibility timeout, or configuring cross-account delivery. Triggers: create sqs fifo queue, fifo queue deduplication, sqs message group id, high throughput fifo, sqs dlq redrive, sqs visibility timeout, sqs sse kms, sqs fifo cross account.'\nlicense: Apache-2.0\ncompatibility: 'Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). For live deployment: AWS CLI v2 with sqs access. Works with Terraform aws_sqs_queue resources and CloudFormation AWS::SQS::Queue templates.'\nmetadata:\n  domain: aws-cloudops\n  complexity: high\n  requires_llm: 'true'\n  phase: '1'\n  supports_pipeline: 'true'\n  entry_point: 'false'\n  family: AppIntegration\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, sqs, fifo, message-queue, cloudops, deploy, provisioning, deduplication, message-group, high-throughput, dlq, redrive, visibility-timeout, sse-kms\n  dependencies: aws-orchestrator\n  keywords: aws, sqs, fifo, message queue, cloudops, deploy, provisioning, deduplication, message group, high throughput, dlq, redrive, visibility timeout, sse kms, cross account\n  when_to_use: Invoke when the user wants to create an SQS FIFO queue, configure message group ID ordering, set up content-based or explicit deduplication, enable high-throughput FIFO mode, attach a dead- letter queue (DLQ), tune visibility timeout, configure SSE-KMS encryption, set up access policies, configure redrive policies, or enable cross-account delivery to a FIFO queue. Do NOT invoke for SQS Standard queues (use standard queue skills), SNS topics, or Amazon MQ.\n---\n\n# SQS FIFO Deployer\n\nAn AWS CloudOps agent skill that provisions Amazon SQS FIFO queues\nwith correct defaults. The skill walks the operator through FIFO\nqueue attributes (FifoQueue=true, ContentBasedDeduplication,\nDeduplicationScope, ThroughputLimit mode), message group ID for\nordering, deduplication strategies (content-based vs explicit\nMessageDeduplicationId), high-throughput FIFO mode, DLQ configuration\nfor FIFO queues, visibility timeout tuning, SSE-KMS encryption, access\npolicy, redrive policy, and cross-account delivery. It captures queue\ntopology and ordering requirements, explains why each default matters,\nand emits a READY_TO_DEPLOY checklist with copy-pasteable verification\ncommands.\n\n## Activation keywords\n\ncreate SQS FIFO queue, FIFO queue deduplication, SQS message group ID,\nhigh throughput FIFO, SQS DLQ redrive, SQS visibility timeout, SQS SSE\nKMS, SQS FIFO cross account.\n\n## STRICT output contract\n\nWhen this skill is invoked with an SQS FIFO provisioning request\n(create a FIFO queue, configure deduplication, set up message group\nordering, enable high-throughput mode, attach a DLQ, configure cross-\naccount delivery, or a partial configuration), the agent MUST respond\nwith the READY_TO_DEPLOY checklist defined in the \"Output format\"\nsection using the literal all-caps labels `SQS_FIFO:`, `VERDICT:`,\n`CHECKLIST:`, and `VERIFICATION_COMMANDS:`. Do NOT preface the\nchecklist with prose, headings, or disclaimers — emit the block as\nthe first lines of the response. This contract is what assertion-based\nevals and downstream provisioning pipelines rely on; deviating from\nthe 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 `[x]`), 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 — FIFO queue attributes | Core FIFO model |\n| Step 2 — Message group ID for ordering | Ordering guarantee |\n| Step 3 — Deduplication (content-based vs explicit) | Dedup strategy |\n| Step 4 — High-throughput FIFO mode | Throughput scaling |\n| Step 5 — DLQ for FIFO | Dead-letter handling |\n| Step 6 — Visibility timeout tuning | Consumer lifecycle |\n| Step 7 — SSE-KMS encryption | Encryption at rest |\n| Step 8 — Access policy | Cross-account + producer\u002Fconsumer |\n| Step 9 — Redrive policy | DLQ movement |\n| Step 10 — Cross-account delivery | Cross-account producers |\n| Step 11 — Recent features | Latest |\n| NEVER do these things | Review before signing off |\n| Output format | The literal checklist template |\n| references\u002Fdeduplication-and-ordering.md | Dedup + ordering detail |\n| references\u002Fdlq-and-throughput.md | DLQ + throughput detail |\n\n## Mindset\n\n→ Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) — the three-misconception mindset behind every FIFO provisioning decision.\n\n## Configuration dependency graph (novel heuristic)\n\nSQS FIFO queue configurations are NOT independent. The queue type\n(FIFO) must be set at creation and is immutable. Deduplication scope\ninteracts with throughput mode. The DLQ must be a FIFO queue (Standard\nDLQs cannot be used with FIFO queues). Visibility timeout interacts\n  with message processing time. Use this graph to sequence\n  provisioning.\n\n| Configuration | Hard dependencies (API error without) | Silent failure \u002F immutability | Enables downstream |\n|---|---|---|---|\n| Queue type (FifoQueue=true) | Queue name ends with `.fifo` | IMMUTABLE after creation — cannot convert Standard to FIFO | ordering, deduplication |\n| Content-based deduplication | FifoQueue=true | when enabled, SQS hashes message body for dedup ID; when disabled, producer must send explicit dedup ID | automatic dedup |\n| DeduplicationScope | FifoQueue=true; ThroughputLimit must also be set | default is `queue`; changing to `messageGroup` enables per-group dedup | high-throughput mode |\n| ThroughputLimit | FifoQueue=true; DeduplicationScope must also be set | default is `perQueue`; changing to `messagesPerGroupId` enables per-group throughput | high-throughput mode |\n| High-throughput FIFO | DeduplicationScope=messageGroup + ThroughputLimit=messagesPerGroupId | both attributes must be set together; setting only one is rejected | 300 TPS per group |\n| DLQ (redrive policy) | DLQ must be a FIFO queue; DLQ must exist before redrive policy is attached | a Standard DLQ CANNOT be used with a FIFO queue — API rejects | dead-letter handling |\n| Visibility timeout | nothing — queue-level attribute | must be >= consumer processing time; too low causes duplicate processing | consumer lifecycle |\n| SSE-KMS encryption | KMS key exists (if customer-managed) | encryption is queue-level; all messages encrypted with the key | encryption at rest |\n| Access policy | nothing — queue-level attribute | cross-account producers\u002Fconsumers need explicit Principal in policy | cross-account delivery |\n| Redrive policy | DLQ ARN known | deadLetterTargetArn + maxReceiveCount; maxReceiveCount must be > 0 | DLQ movement |\n| Cross-account delivery | Access policy on the queue permits sender account | sender account needs sqs:SendMessage permission | cross-account producers |\n\n**The message-group-and-deduplication row is the one a baseline model\nmisses.** Creating the FIFO queue is necessary but NOT sufficient. The\nmessage group ID determines ordering parallelism. The deduplication\nstrategy (content-based vs explicit) determines duplicate prevention.\nThe high-throughput mode requires BOTH DeduplicationScope and\nThroughputLimit to be set together. The procedure below forces an\nexplicit decision on each.\n\n**Cross-dependency gotchas:**\n- The `.fifo` suffix in the queue name is MANDATORY. A queue named\n  `my-queue` without `.fifo` cannot have FifoQueue=true.\n- The DLQ for a FIFO queue MUST also be a FIFO queue. A Standard DLQ\n  is rejected by the API.\n- High-throughput mode requires setting BOTH DeduplicationScope and\n  ThroughputLimit. Setting only one results in an API error.\n- ContentBasedDeduplication=true generates dedup IDs from message body\n  hashes. If the producer sends explicit dedup IDs, this attribute is\n  ignored for those messages.\n- Visibility timeout must be longer than the consumer's processing\n  time. If it expires before the consumer deletes the message, the\n  message becomes visible again and may be processed twice.\n\n## Expert heuristic: message group ID partitioning for parallelism\n\n→ Moved to [references\u002Fdeduplication-and-ordering.md](references\u002Fdeduplication-and-ordering.md) — the group-ID partitioning\u002Fparallelism model.\n\n## Expert heuristic: deduplication ID management\n\n→ Moved to [references\u002Fdeduplication-and-ordering.md](references\u002Fdeduplication-and-ordering.md) — content-based vs explicit vs per-group dedup strategies and the 5-minute window.\n\n## Expert heuristic: high-throughput FIFO quota caveats\n\n→ Moved to [references\u002Fdlq-and-throughput.md](references\u002Fdlq-and-throughput.md) — dedup-scope, quota, cost, and rollback caveats.\n\n## Prerequisites (verify before provisioning)\n\nBefore emitting provisioning commands, verify these prerequisites. If\nany are missing, the verdict is **PREREQUISITES_MISSING**.\n\n| Prerequisite | Why it matters | How to verify |\n|---|---|---|\n| Queue name ends with `.fifo` | Mandatory for FIFO queues | Verify naming convention |\n| FIFO vs Standard decision | FIFO type is immutable after creation | Assess ordering requirements |\n| Deduplication strategy decided | Content-based vs explicit dedup ID | Assess dedup requirements |\n| DLQ is also FIFO (if using DLQ) | Standard DLQ cannot attach to FIFO queue | `aws sqs get-queue-attributes --queue-url \u003Cdlq-url> --attribute-names FifoQueue` |\n| KMS key ARN (if using SSE-KMS) | Customer-managed key for encryption | `aws kms describe-key --key-id \u003Cid>` |\n| Consumer processing time (for visibility timeout) | Visibility timeout must exceed processing time | Assess consumer workload |\n| Cross-account IDs (if cross-account delivery) | Access policy needs principal account IDs | `aws sts get-caller-identity` |\n| IAM permissions for SQS actions | sqs:CreateQueue, SetQueueAttributes, etc. | `aws iam list-attached-role-policies` |\n\nIf any prerequisite is missing, output `VERDICT: PREREQUISITES_MISSING`\nand cite the specific gap.\n\n## Step 1 — FIFO queue attributes\n\nFIFO queues require specific attributes at creation time. These are\nimmutable after the queue is created.\n\n```bash\nQUEUE_URL=$(aws sqs create-queue \\\n  --queue-name \"order-processing.fifo\" \\\n  --attributes \"FifoQueue=true,ContentBasedDeduplication=true,VisibilityTimeout=60,DelaySeconds=0,MessageRetentionPeriod=345600\" \\\n  --query 'QueueUrl' --output text)\n\necho \"Queue URL: $QUEUE_URL\"\n```\n\n**Key FIFO attributes:**\n\n| Attribute | Default | Description |\n|---|---|---|\n| FifoQueue | false (must set true) | Enables FIFO ordering — immutable after creation |\n| ContentBasedDeduplication | false | Generates dedup ID from message body hash |\n| DeduplicationScope | queue | Set to `messageGroup` for high-throughput |\n| ThroughputLimit | perQueue | Set to `messagesPerGroupId` for high-throughput |\n| VisibilityTimeout | 30 | Seconds before message becomes visible again after receive |\n| MessageRetentionPeriod | 345600 (4 days) | How long messages are retained |\n| DelaySeconds | 0 | Per-queue delay for message delivery |\n\n**Verify the queue:**\n\n```bash\naws sqs get-queue-attributes \\\n  --queue-url \"$QUEUE_URL\" \\\n  --attribute-names \"QueueArn,FifoQueue,ContentBasedDeduplication,DeduplicationScope,ThroughputLimit,VisibilityTimeout\"\n```\n\n## Step 2 — Message group ID for ordering\n\nThe message group ID (`MessageGroupId`) is the ordering partition.\nMessages with the same group ID are processed in FIFO order.\nMessages with different group IDs are processed in parallel.\n\n```bash\n# Send messages with different group IDs (parallel processing)\naws sqs send-message \\\n  --queue-url \"$QUEUE_URL\" \\\n  --message-body '{\"orderId\": \"order-001\", \"status\": \"created\"}' \\\n  --message-group-id \"customer-123\"\n\naws sqs send-message \\\n  --queue-url \"$QUEUE_URL\" \\\n  --message-body '{\"orderId\": \"order-002\", \"status\": \"created\"}' \\\n  --message-group-id \"customer-456\"\n```\n\n**Receive messages:**\n\n```bash\naws sqs receive-message \\\n  --queue-url \"$QUEUE_URL\" \\\n  --max-number-of-messages 10 \\\n  --wait-time-seconds 20\n```\n\n**Key:** messages from the same group are returned in order. Messages\nfrom different groups can be received by different consumers in\nparallel.\n\n## Step 3 — Deduplication (content-based vs explicit)\n\n### Content-based deduplication\n\nWhen `ContentBasedDeduplication=true`, SQS generates a deduplication\nID from the SHA-256 hash of the message body.\n\n```bash\n# Content-based dedup — same body within 5 min is NOT re-enqueued\naws sqs send-message \\\n  --queue-url \"$QUEUE_URL\" \\\n  --message-body '{\"orderId\": \"order-001\"}' \\\n  --message-group-id \"customer-123\"\n\n# This second message with the SAME body is silently dropped (within 5 min)\naws sqs send-message \\\n  --queue-url \"$QUEUE_URL\" \\\n  --message-body '{\"orderId\": \"order-001\"}' \\\n  --message-group-id \"customer-123\"\n```\n\n### Explicit deduplication ID\n\nWhen `ContentBasedDeduplication=false` (or overridden), the producer\nsends an explicit `MessageDeduplicationId`.\n\n```bash\n# Explicit dedup — producer controls dedup semantics\naws sqs send-message \\\n  --queue-url \"$QUEUE_URL\" \\\n  --message-body '{\"orderId\": \"order-001\", \"timestamp\": \"2026-01-01T10:00:00Z\"}' \\\n  --message-group-id \"customer-123\" \\\n  --message-deduplication-id \"order-001\"\n```\n\n**Key:** use explicit dedup when the same logical message may have\ndifferent bodies (e.g., retries with updated timestamps). Use a stable\nbusiness key as the dedup ID.\n\n## Step 4 — High-throughput FIFO mode\n\nHigh-throughput FIFO mode requires setting BOTH DeduplicationScope and\nThroughputLimit. This enables per-message-group throughput scaling.\n\n```bash\n# High-throughput FIFO queue\nQUEUE_URL=$(aws sqs create-queue \\\n  --queue-name \"high-throughput-orders.fifo\" \\\n  --attributes \"FifoQueue=true,DeduplicationScope=messageGroup,ThroughputLimit=messagesPerGroupId,VisibilityTimeout=60\" \\\n  --query 'QueueUrl' --output text)\n```\n\n**Critical:** both `DeduplicationScope=messageGroup` and\n`ThroughputLimit=messagesPerGroupId` must be set together. Setting\nonly one results in an API error.\n\n**Throughput comparison:**\n\n```text\nStandard FIFO:        300 TPS per API action (shared across all groups)\nHigh-throughput FIFO:  300 TPS per API action PER message group\n                       10 groups = 3,000 TPS\n                       100 groups = 30,000 TPS\n```\n\n## Step 5 — DLQ for FIFO\n\nThe DLQ for a FIFO queue MUST also be a FIFO queue. A Standard queue\ncannot serve as a DLQ for a FIFO queue.\n\n```bash\nDLQ_URL=$(aws sqs create-queue \\\n  --queue-name \"order-processing-dlq.fifo\" \\\n  --attributes \"FifoQueue=true\" --query 'QueueUrl' --output text)\n\nDLQ_ARN=$(aws sqs get-queue-attributes --queue-url \"$DLQ_URL\" \\\n  --attribute-names \"QueueArn\" --query 'Attributes.QueueArn' --output text)\n\naws sqs set-queue-attributes --queue-url \"$QUEUE_URL\" \\\n  --attributes \"RedrivePolicy={\\\"deadLetterTargetArn\\\":\\\"${DLQ_ARN}\\\",\\\"maxReceiveCount\\\":\\\"5\\\"}\"\n```\n\n**Key:** `maxReceiveCount` determines how many times a message is\nreceived before it is moved to the DLQ. See Step 9 for redrive.\n\n## Step 6 — Visibility timeout tuning\n\nThe visibility timeout determines how long a message is invisible to\nother consumers after being received. If the consumer does not delete\nthe message before the timeout expires, the message becomes visible\nagain and may be processed by another consumer (causing duplicates).\n\n```bash\naws sqs set-queue-attributes --queue-url \"$QUEUE_URL\" \\\n  --attributes \"VisibilityTimeout=120\"\n```\n\n**Guidelines:** set the visibility timeout to AT LEAST 2x the expected\nprocessing time. Use `change-message-visibility` for per-message\noverrides. See `references\u002Fdlq-and-throughput.md` for the full tuning\ntable.\n\n## Step 7 — SSE-KMS encryption\n\nSSE-KMS encrypts messages at rest using a KMS key (AWS-managed or\ncustomer-managed).\n\n```bash\naws sqs set-queue-attributes --queue-url \"$QUEUE_URL\" \\\n  --attributes \"KmsMasterKeyId=arn:aws:kms:us-east-1:123456789012:key\u002Fabc123,KmsDataKeyReusePeriodSeconds=300\"\n```\n\nThe KMS key policy must allow SQS to `kms:GenerateDataKey` and\n`kms:Decrypt`. For cross-account producers, the key policy must also\nallow those accounts. See `references\u002Fdlq-and-throughput.md` for KMS\nkey policy examples.\n\n## Step 8 — Access policy\n\nThe queue access policy controls who can send and receive messages.\nBy default, only the queue owner can access the queue. For\ncross-account delivery, grant `sqs:SendMessage` to the producer's\naccount and ensure the producer's IAM role also permits it.\n\n## Step 9 — Redrive policy\n\nThe redrive policy defines the DLQ and `maxReceiveCount`. Messages\nthat exceed `maxReceiveCount` are moved to the DLQ.\n\n```bash\n# Redrive from DLQ back to the main queue\naws sqs start-message-move-task \\\n  --source-arn \"$DLQ_ARN\" \\\n  --destination-arn \"$MAIN_QUEUE_ARN\" --query 'TaskHandle' --output text\n```\n\n**Key:** `StartMessageMoveTask` is the modern API for moving messages\nfrom a DLQ back to the source queue. It preserves message attributes.\n\n## Step 10 — Cross-account delivery\n\nCross-account delivery allows producers in one account to send\nmessages to a FIFO queue in another account. This requires:\n\n1. The queue access policy grants `sqs:SendMessage` to the producer\n   account.\n2. The producer's IAM role allows `sqs:SendMessage` to the queue.\n3. If SSE-KMS is enabled, the KMS key policy allows the producer\n   account.\n\nSee `references\u002Fdlq-and-throughput.md` for a full cross-account\naccess policy example with Terraform.\n\n**Key:** for FIFO queues, cross-account messages must include both\n`MessageGroupId` and `MessageDeduplicationId` (or the queue must have\n`ContentBasedDeduplication=true`).\n\n## Step 11 — Recent features\n\n→ Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) — recent AWS features (2023-2026).\n\n## NEVER do these things\n\n1. **NEVER use a Standard queue as a DLQ for a FIFO queue.** The DLQ\n   for a FIFO queue MUST also be a FIFO queue. The API will reject a\n   redrive policy pointing to a Standard queue DLQ.\n\n2. **NEVER omit the `.fifo` suffix in the queue name.** FIFO queue\n   names MUST end with `.fifo`. The API rejects\n   `create-queue --queue-name \"my-queue\" --attributes \"FifoQueue=true\"`\n   without the suffix.\n\n3. **NEVER use a single message group ID for all messages.** A single\n   group ID serializes ALL messages through one consumer, eliminating\n   parallelism. Use per-entity group IDs (e.g., customer ID, order ID)\n   to scale throughput.\n\n4. **NEVER set DeduplicationScope or ThroughputLimit alone.**\n   High-throughput FIFO mode requires BOTH\n   `DeduplicationScope=messageGroup` AND\n   `ThroughputLimit=messagesPerGroupId`. Setting only one results in\n   an API error.\n\n5. **NEVER assume content-based deduplication catches logical\n   duplicates.** Content-based dedup hashes the message BODY. Two\n   messages with different bodies but the same logical content (e.g.,\n   an order retry with a new timestamp) are NOT deduplicated. Use\n   explicit `MessageDeduplicationId` for semantic dedup.\n\n6. **NEVER set visibility timeout lower than the consumer processing\n   time.** If the timeout expires before the consumer deletes the\n   message, the message becomes visible again and may be processed\n   twice. Set the timeout to at least 2x the expected processing time.\n\n7. **NEVER assume high-throughput mode is free.** High-throughput FIFO\n   has a different pricing tier (higher per-request cost), changes\n   deduplication scope from queue-level to group-level, and counts\n   against a separate account quota. Evaluate all three before\n   enabling.\n\n8. **NEVER forget MessageGroupId when sending to a FIFO queue.** Every\n   message sent to a FIFO queue MUST include a `MessageGroupId`.\n   Without it, the API rejects the message.\n\n9. **NEVER convert a Standard queue to FIFO or vice versa.** The\n   queue type (FifoQueue attribute) is IMMUTABLE after creation. To\n   change types, create a new queue and migrate consumers\u002Fproducers.\n\n10. **NEVER assume cross-account delivery works without access policy\n    AND IAM permissions.** Cross-account delivery requires BOTH: (1)\n    the queue access policy grants `sqs:SendMessage` to the producer's\n    account, AND (2) the producer's IAM role allows `sqs:SendMessage`\n    to the queue. Both sides must be configured.\n\n## Output format\n\n```text\nSQS_FIFO: \u003Cqueue-name> (\u003Cqueue-url>)\nVERDICT: READY_TO_DEPLOY | PREREQUISITES_MISSING\nCHECKLIST:\n  [✓|✗] Queue name: \u003Cname>.fifo\n  [✓|✗] FifoQueue: true (immutable)\n  [✓|✗] ContentBasedDeduplication: true | false (explicit dedup ID)\n  [✓|✗] DeduplicationScope: queue | messageGroup\n  [✓|✗] ThroughputLimit: perQueue | messagesPerGroupId\n  [✓|✗] High-throughput mode: enabled (per-group dedup + throughput) | disabled\n  [✓|✗] Message group ID strategy: \u003Cper-entity|single-group> — \u003Cdescription>\n  [✓|✗] Visibility timeout: \u003Cseconds> (consumer processing time estimate: \u003Cseconds>)\n  [✓|✗] DLQ: \u003Cdlq-name>.fifo (\u003Cdlq-arn>) — maxReceiveCount: \u003Ccount> | None\n  [✓|✗] SSE-KMS encryption: enabled (\u003Ckey-arn>) | disabled\n  [✓|✗] Access policy: \u003Csame-account|cross-account> — \u003Cdescription>\n  [✓|✗] Redrive policy: configured (maxReceiveCount=\u003Ccount>) | not configured\n  [✓|✗] Cross-account delivery: enabled (producer accounts: \u003Clist>) | disabled\n  [✓|✗] Tags: \u003Ckey=value list>\nVERIFICATION_COMMANDS:\n  aws sqs get-queue-attributes --queue-url \u003Curl> --attribute-names All\n  aws sqs get-queue-attributes --queue-url \u003Cdlq-url> --attribute-names All\n```\n\n### Worked example — standard FIFO with deduplication, DLQ, and SSE-KMS\n\n```text\nSQS_FIFO: order-processing.fifo (https:\u002F\u002Fsqs.us-east-1.amazonaws.com\u002F123456789012\u002Forder-processing.fifo)\nVERDICT: READY_TO_DEPLOY\nCHECKLIST:\n  [✓] Queue name: order-processing.fifo\n  [✓] FifoQueue: true (immutable)\n  [✓] ContentBasedDeduplication: false (explicit dedup ID)\n  [✓] DeduplicationScope: queue\n  [✓] ThroughputLimit: perQueue\n  [✓] High-throughput mode: disabled\n  [✓] Message group ID strategy: per-entity (customer ID) — per-customer ordering with parallel processing\n  [✓] Visibility timeout: 120 (consumer processing time estimate: 60s)\n  [✓] DLQ: order-processing-dlq.fifo (arn:aws:sqs:us-east-1:123456789012:order-processing-dlq.fifo) — maxReceiveCount: 5\n  [✓] SSE-KMS encryption: enabled (arn:aws:kms:us-east-1:123456789012:key\u002Fabc123)\n  [✓] Access policy: cross-account — producer account 999999999999 granted sqs:SendMessage\n  [✓] Redrive policy: configured (maxReceiveCount=5)\n  [✓] Cross-account delivery: enabled (producer accounts: 999999999999)\n  [✓] Tags: Environment=production, Application=order-service\nVERIFICATION_COMMANDS:\n  aws sqs get-queue-attributes --queue-url https:\u002F\u002Fsqs.us-east-1.amazonaws.com\u002F123456789012\u002Forder-processing.fifo --attribute-names All\n  aws sqs get-queue-attributes --queue-url https:\u002F\u002Fsqs.us-east-1.amazonaws.com\u002F123456789012\u002Forder-processing-dlq.fifo --attribute-names All\n```\n\n## Error handling\n\n→ Moved to [references\u002Ferror-handling.md](references\u002Ferror-handling.md) — symptom → cause → fix for delivery, duplicate processing, throughput, DLQ, and cross-account failures.\n\n## References (load on demand)\n\n- [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) — Mindset (three FIFO misconceptions) and recent AWS features (2023-2026).\n- [references\u002Ferror-handling.md](references\u002Ferror-handling.md) — error-handling deep dive: message delivery, duplicate processing, throughput limits, DLQ attachment, cross-account failures.\n- [references\u002Fdeduplication-and-ordering.md](references\u002Fdeduplication-and-ordering.md) — pre-existing; extended with the message-group-ID partitioning and deduplication-ID management heuristics moved from SKILL.md.\n- [references\u002Fdlq-and-throughput.md](references\u002Fdlq-and-throughput.md) — pre-existing; extended with the high-throughput FIFO quota caveats moved from SKILL.md.\n\n## Domain\n\nAWS CloudOps \u002F Amazon SQS FIFO Queue Provisioning and Message\nOrdering.\n\n## AWS documentation\n\n- **SQS FIFO queues** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAWSSimpleQueueService\u002Flatest\u002FSQSDeveloperGuide\u002Fsqs-fifo-queues.html\n- **Deduplication** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAWSSimpleQueueService\u002Flatest\u002FSQSDeveloperGuide\u002Fusing-messagededuplicationid-property.html\n- **High-throughput FIFO** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAWSSimpleQueueService\u002Flatest\u002FSQSDeveloperGuide\u002Fquotas-queues.html\n- **DLQ and redrive** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAWSSimpleQueueService\u002Flatest\u002FSQSDeveloperGuide\u002Fsqs-dead-letter-queues.html\n- **SSE-KMS** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAWSSimpleQueueService\u002Flatest\u002FSQSDeveloperGuide\u002Fsqs-server-side-encryption.html\n","# SQS FIFO Deployer\n\nAn AWS CloudOps agent skill that provisions Amazon SQS FIFO queues\nwith correct defaults. The skill walks the operator through FIFO\nqueue attributes (FifoQueue=true, ContentBasedDeduplication,\nDeduplicationScope, ThroughputLimit mode), message group ID for\nordering, deduplication strategies (content-based vs explicit\nMessageDeduplicationId), high-throughput FIFO mode, DLQ configuration\nfor FIFO queues, visibility timeout tuning, SSE-KMS encryption, access\npolicy, redrive policy, and cross-account delivery. It captures queue\ntopology and ordering requirements, explains why each default matters,\nand emits a READY_TO_DEPLOY checklist with copy-pasteable verification\ncommands.\n\n## Activation keywords\n\ncreate SQS FIFO queue, FIFO queue deduplication, SQS message group ID,\nhigh throughput FIFO, SQS DLQ redrive, SQS visibility timeout, SQS SSE\nKMS, SQS FIFO cross account.\n\n## STRICT output contract\n\nWhen this skill is invoked with an SQS FIFO provisioning request\n(create a FIFO queue, configure deduplication, set up message group\nordering, enable high-throughput mode, attach a DLQ, configure cross-\naccount delivery, or a partial configuration), the agent MUST respond\nwith the READY_TO_DEPLOY checklist defined in the \"Output format\"\nsection using the literal all-caps labels `SQS_FIFO:`, `VERDICT:`,\n`CHECKLIST:`, and `VERIFICATION_COMMANDS:`. Do NOT preface the\nchecklist with prose, headings, or disclaimers — emit the block as\nthe first lines of the response. This contract is what assertion-based\nevals and downstream provisioning pipelines rely on; deviating from\nthe 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 `[x]`), 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 — FIFO queue attributes | Core FIFO model |\n| Step 2 — Message group ID for ordering | Ordering guarantee |\n| Step 3 — Deduplication (content-based vs explicit) | Dedup strategy |\n| Step 4 — High-throughput FIFO mode | Throughput scaling |\n| Step 5 — DLQ for FIFO | Dead-letter handling |\n| Step 6 — Visibility timeout tuning | Consumer lifecycle |\n| Step 7 — SSE-KMS encryption | Encryption at rest |\n| Step 8 — Access policy | Cross-account + producer\u002Fconsumer |\n| Step 9 — Redrive policy | DLQ movement |\n| Step 10 — Cross-account delivery | Cross-account producers |\n| Step 11 — Recent features | Latest |\n| NEVER do these things | Review before signing off |\n| Output format | The literal checklist template |\n| references\u002Fdeduplication-and-ordering.md | Dedup + ordering detail |\n| references\u002Fdlq-and-throughput.md | DLQ + throughput detail |\n\n## Mindset\n\n→ Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) — the three-misconception mindset behind every FIFO provisioning decision.\n\n## Configuration dependency graph (novel heuristic)\n\nSQS FIFO queue configurations are NOT independent. The queue type\n(FIFO) must be set at creation and is immutable. Deduplication scope\ninteracts with throughput mode. The DLQ must be a FIFO queue (Standard\nDLQs cannot be used with FIFO queues). Visibility timeout interacts\n  with message processing time. Use this graph to sequence\n  provisioning.\n\n| Configuration | Hard dependencies (API error without) | Silent failure \u002F immutability | Enables downstream |\n|---|---|---|---|\n| Queue type (FifoQueue=true) | Queue name ends with `.fifo` | IMMUTABLE after creation — cannot convert Standard to FIFO | ordering, deduplication |\n| Content-based deduplication | FifoQueue=true | when enabled, SQS hashes message body for dedup ID; when disabled, producer must send explicit dedup ID | automatic dedup |\n| DeduplicationScope | FifoQueue=true; ThroughputLimit must also be set | default is `queue`; changing to `messageGroup` enables per-group dedup | high-throughput mode |\n| ThroughputLimit | FifoQueue=true; DeduplicationScope must also be set | default is `perQueue`; changing to `messagesPerGroupId` enables per-group throughput | high-throughput mode |\n| High-throughput FIFO | DeduplicationScope=messageGroup + ThroughputLimit=messagesPerGroupId | both attributes must be set together; setting only one is rejected | 300 TPS per group |\n| DLQ (redrive policy) | DLQ must be a FIFO queue; DLQ must exist before redrive policy is attached | a Standard DLQ CANNOT be used with a FIFO queue — API rejects | dead-letter handling |\n| Visibility timeout | nothing — queue-level attribute | must be >= consumer processing time; too low causes duplicate processing | consumer lifecycle |\n| SSE-KMS encryption | KMS key exists (if customer-managed) | encryption is queue-level; all messages encrypted with the key | encryption at rest |\n| Access policy | nothing — queue-level attribute | cross-account producers\u002Fconsumers need explicit Principal in policy | cross-account delivery |\n| Redrive policy | DLQ ARN known | deadLetterTargetArn + maxReceiveCount; maxReceiveCount must be > 0 | DLQ movement |\n| Cross-account delivery | Access policy on the queue permits sender account | sender account needs sqs:SendMessage permission | cross-account producers |\n\n**The message-group-and-deduplication row is the one a baseline model\nmisses.** Creating the FIFO queue is necessary but NOT sufficient. The\nmessage group ID determines ordering parallelism. The deduplication\nstrategy (content-based vs explicit) determines duplicate prevention.\nThe high-throughput mode requires BOTH DeduplicationScope and\nThroughputLimit to be set together. The procedure below forces an\nexplicit decision on each.\n\n**Cross-dependency gotchas:**\n- The `.fifo` suffix in the queue name is MANDATORY. A queue named\n  `my-queue` without `.fifo` cannot have FifoQueue=true.\n- The DLQ for a FIFO queue MUST also be a FIFO queue. A Standard DLQ\n  is rejected by the API.\n- High-throughput mode requires setting BOTH DeduplicationScope and\n  ThroughputLimit. Setting only one results in an API error.\n- ContentBasedDeduplication=true generates dedup IDs from message body\n  hashes. If the producer sends explicit dedup IDs, this attribute is\n  ignored for those messages.\n- Visibility timeout must be longer than the consumer's processing\n  time. If it expires before the consumer deletes the message, the\n  message becomes visible again and may be processed twice.\n\n## Expert heuristic: message group ID partitioning for parallelism\n\n→ Moved to [references\u002Fdeduplication-and-ordering.md](references\u002Fdeduplication-and-ordering.md) — the group-ID partitioning\u002Fparallelism model.\n\n## Expert heuristic: deduplication ID management\n\n→ Moved to [references\u002Fdeduplication-and-ordering.md](references\u002Fdeduplication-and-ordering.md) — content-based vs explicit vs per-group dedup strategies and the 5-minute window.\n\n## Expert heuristic: high-throughput FIFO quota caveats\n\n→ Moved to [references\u002Fdlq-and-throughput.md](references\u002Fdlq-and-throughput.md) — dedup-scope, quota, cost, and rollback caveats.\n\n## Prerequisites (verify before provisioning)\n\nBefore emitting provisioning commands, verify these prerequisites. If\nany are missing, the verdict is **PREREQUISITES_MISSING**.\n\n| Prerequisite | Why it matters | How to verify |\n|---|---|---|\n| Queue name ends with `.fifo` | Mandatory for FIFO queues | Verify naming convention |\n| FIFO vs Standard decision | FIFO type is immutable after creation | Assess ordering requirements |\n| Deduplication strategy decided | Content-based vs explicit dedup ID | Assess dedup requirements |\n| DLQ is also FIFO (if using DLQ) | Standard DLQ cannot attach to FIFO queue | `aws sqs get-queue-attributes --queue-url \u003Cdlq-url> --attribute-names FifoQueue` |\n| KMS key ARN (if using SSE-KMS) | Customer-managed key for encryption | `aws kms describe-key --key-id \u003Cid>` |\n| Consumer processing time (for visibility timeout) | Visibility timeout must exceed processing time | Assess consumer workload |\n| Cross-account IDs (if cross-account delivery) | Access policy needs principal account IDs | `aws sts get-caller-identity` |\n| IAM permissions for SQS actions | sqs:CreateQueue, SetQueueAttributes, etc. | `aws iam list-attached-role-policies` |\n\nIf any prerequisite is missing, output `VERDICT: PREREQUISITES_MISSING`\nand cite the specific gap.\n\n## Step 1 — FIFO queue attributes\n\nFIFO queues require specific attributes at creation time. These are\nimmutable after the queue is created.\n\n```bash\nQUEUE_URL=$(aws sqs create-queue \\\n  --queue-name \"order-processing.fifo\" \\\n  --attributes \"FifoQueue=true,ContentBasedDeduplication=true,VisibilityTimeout=60,DelaySeconds=0,MessageRetentionPeriod=345600\" \\\n  --query 'QueueUrl' --output text)\n\necho \"Queue URL: $QUEUE_URL\"\n```\n\n**Key FIFO attributes:**\n\n| Attribute | Default | Description |\n|---|---|---|\n| FifoQueue | false (must set true) | Enables FIFO ordering — immutable after creation |\n| ContentBasedDeduplication | false | Generates dedup ID from message body hash |\n| DeduplicationScope | queue | Set to `messageGroup` for high-throughput |\n| ThroughputLimit | perQueue | Set to `messagesPerGroupId` for high-throughput |\n| VisibilityTimeout | 30 | Seconds before message becomes visible again after receive |\n| MessageRetentionPeriod | 345600 (4 days) | How long messages are retained |\n| DelaySeconds | 0 | Per-queue delay for message delivery |\n\n**Verify the queue:**\n\n```bash\naws sqs get-queue-attributes \\\n  --queue-url \"$QUEUE_URL\" \\\n  --attribute-names \"QueueArn,FifoQueue,ContentBasedDeduplication,DeduplicationScope,ThroughputLimit,VisibilityTimeout\"\n```\n\n## Step 2 — Message group ID for ordering\n\nThe message group ID (`MessageGroupId`) is the ordering partition.\nMessages with the same group ID are processed in FIFO order.\nMessages with different group IDs are processed in parallel.\n\n```bash\n# Send messages with different group IDs (parallel processing)\naws sqs send-message \\\n  --queue-url \"$QUEUE_URL\" \\\n  --message-body '{\"orderId\": \"order-001\", \"status\": \"created\"}' \\\n  --message-group-id \"customer-123\"\n\naws sqs send-message \\\n  --queue-url \"$QUEUE_URL\" \\\n  --message-body '{\"orderId\": \"order-002\", \"status\": \"created\"}' \\\n  --message-group-id \"customer-456\"\n```\n\n**Receive messages:**\n\n```bash\naws sqs receive-message \\\n  --queue-url \"$QUEUE_URL\" \\\n  --max-number-of-messages 10 \\\n  --wait-time-seconds 20\n```\n\n**Key:** messages from the same group are returned in order. Messages\nfrom different groups can be received by different consumers in\nparallel.\n\n## Step 3 — Deduplication (content-based vs explicit)\n\n### Content-based deduplication\n\nWhen `ContentBasedDeduplication=true`, SQS generates a deduplication\nID from the SHA-256 hash of the message body.\n\n```bash\n# Content-based dedup — same body within 5 min is NOT re-enqueued\naws sqs send-message \\\n  --queue-url \"$QUEUE_URL\" \\\n  --message-body '{\"orderId\": \"order-001\"}' \\\n  --message-group-id \"customer-123\"\n\n# This second message with the SAME body is silently dropped (within 5 min)\naws sqs send-message \\\n  --queue-url \"$QUEUE_URL\" \\\n  --message-body '{\"orderId\": \"order-001\"}' \\\n  --message-group-id \"customer-123\"\n```\n\n### Explicit deduplication ID\n\nWhen `ContentBasedDeduplication=false` (or overridden), the producer\nsends an explicit `MessageDeduplicationId`.\n\n```bash\n# Explicit dedup — producer controls dedup semantics\naws sqs send-message \\\n  --queue-url \"$QUEUE_URL\" \\\n  --message-body '{\"orderId\": \"order-001\", \"timestamp\": \"2026-01-01T10:00:00Z\"}' \\\n  --message-group-id \"customer-123\" \\\n  --message-deduplication-id \"order-001\"\n```\n\n**Key:** use explicit dedup when the same logical message may have\ndifferent bodies (e.g., retries with updated timestamps). Use a stable\nbusiness key as the dedup ID.\n\n## Step 4 — High-throughput FIFO mode\n\nHigh-throughput FIFO mode requires setting BOTH DeduplicationScope and\nThroughputLimit. This enables per-message-group throughput scaling.\n\n```bash\n# High-throughput FIFO queue\nQUEUE_URL=$(aws sqs create-queue \\\n  --queue-name \"high-throughput-orders.fifo\" \\\n  --attributes \"FifoQueue=true,DeduplicationScope=messageGroup,ThroughputLimit=messagesPerGroupId,VisibilityTimeout=60\" \\\n  --query 'QueueUrl' --output text)\n```\n\n**Critical:** both `DeduplicationScope=messageGroup` and\n`ThroughputLimit=messagesPerGroupId` must be set together. Setting\nonly one results in an API error.\n\n**Throughput comparison:**\n\n```text\nStandard FIFO:        300 TPS per API action (shared across all groups)\nHigh-throughput FIFO:  300 TPS per API action PER message group\n                       10 groups = 3,000 TPS\n                       100 groups = 30,000 TPS\n```\n\n## Step 5 — DLQ for FIFO\n\nThe DLQ for a FIFO queue MUST also be a FIFO queue. A Standard queue\ncannot serve as a DLQ for a FIFO queue.\n\n```bash\nDLQ_URL=$(aws sqs create-queue \\\n  --queue-name \"order-processing-dlq.fifo\" \\\n  --attributes \"FifoQueue=true\" --query 'QueueUrl' --output text)\n\nDLQ_ARN=$(aws sqs get-queue-attributes --queue-url \"$DLQ_URL\" \\\n  --attribute-names \"QueueArn\" --query 'Attributes.QueueArn' --output text)\n\naws sqs set-queue-attributes --queue-url \"$QUEUE_URL\" \\\n  --attributes \"RedrivePolicy={\\\"deadLetterTargetArn\\\":\\\"${DLQ_ARN}\\\",\\\"maxReceiveCount\\\":\\\"5\\\"}\"\n```\n\n**Key:** `maxReceiveCount` determines how many times a message is\nreceived before it is moved to the DLQ. See Step 9 for redrive.\n\n## Step 6 — Visibility timeout tuning\n\nThe visibility timeout determines how long a message is invisible to\nother consumers after being received. If the consumer does not delete\nthe message before the timeout expires, the message becomes visible\nagain and may be processed by another consumer (causing duplicates).\n\n```bash\naws sqs set-queue-attributes --queue-url \"$QUEUE_URL\" \\\n  --attributes \"VisibilityTimeout=120\"\n```\n\n**Guidelines:** set the visibility timeout to AT LEAST 2x the expected\nprocessing time. Use `change-message-visibility` for per-message\noverrides. See `references\u002Fdlq-and-throughput.md` for the full tuning\ntable.\n\n## Step 7 — SSE-KMS encryption\n\nSSE-KMS encrypts messages at rest using a KMS key (AWS-managed or\ncustomer-managed).\n\n```bash\naws sqs set-queue-attributes --queue-url \"$QUEUE_URL\" \\\n  --attributes \"KmsMasterKeyId=arn:aws:kms:us-east-1:123456789012:key\u002Fabc123,KmsDataKeyReusePeriodSeconds=300\"\n```\n\nThe KMS key policy must allow SQS to `kms:GenerateDataKey` and\n`kms:Decrypt`. For cross-account producers, the key policy must also\nallow those accounts. See `references\u002Fdlq-and-throughput.md` for KMS\nkey policy examples.\n\n## Step 8 — Access policy\n\nThe queue access policy controls who can send and receive messages.\nBy default, only the queue owner can access the queue. For\ncross-account delivery, grant `sqs:SendMessage` to the producer's\naccount and ensure the producer's IAM role also permits it.\n\n## Step 9 — Redrive policy\n\nThe redrive policy defines the DLQ and `maxReceiveCount`. Messages\nthat exceed `maxReceiveCount` are moved to the DLQ.\n\n```bash\n# Redrive from DLQ back to the main queue\naws sqs start-message-move-task \\\n  --source-arn \"$DLQ_ARN\" \\\n  --destination-arn \"$MAIN_QUEUE_ARN\" --query 'TaskHandle' --output text\n```\n\n**Key:** `StartMessageMoveTask` is the modern API for moving messages\nfrom a DLQ back to the source queue. It preserves message attributes.\n\n## Step 10 — Cross-account delivery\n\nCross-account delivery allows producers in one account to send\nmessages to a FIFO queue in another account. This requires:\n\n1. The queue access policy grants `sqs:SendMessage` to the producer\n   account.\n2. The producer's IAM role allows `sqs:SendMessage` to the queue.\n3. If SSE-KMS is enabled, the KMS key policy allows the producer\n   account.\n\nSee `references\u002Fdlq-and-throughput.md` for a full cross-account\naccess policy example with Terraform.\n\n**Key:** for FIFO queues, cross-account messages must include both\n`MessageGroupId` and `MessageDeduplicationId` (or the queue must have\n`ContentBasedDeduplication=true`).\n\n## Step 11 — Recent features\n\n→ Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) — recent AWS features (2023-2026).\n\n## NEVER do these things\n\n1. **NEVER use a Standard queue as a DLQ for a FIFO queue.** The DLQ\n   for a FIFO queue MUST also be a FIFO queue. The API will reject a\n   redrive policy pointing to a Standard queue DLQ.\n\n2. **NEVER omit the `.fifo` suffix in the queue name.** FIFO queue\n   names MUST end with `.fifo`. The API rejects\n   `create-queue --queue-name \"my-queue\" --attributes \"FifoQueue=true\"`\n   without the suffix.\n\n3. **NEVER use a single message group ID for all messages.** A single\n   group ID serializes ALL messages through one consumer, eliminating\n   parallelism. Use per-entity group IDs (e.g., customer ID, order ID)\n   to scale throughput.\n\n4. **NEVER set DeduplicationScope or ThroughputLimit alone.**\n   High-throughput FIFO mode requires BOTH\n   `DeduplicationScope=messageGroup` AND\n   `ThroughputLimit=messagesPerGroupId`. Setting only one results in\n   an API error.\n\n5. **NEVER assume content-based deduplication catches logical\n   duplicates.** Content-based dedup hashes the message BODY. Two\n   messages with different bodies but the same logical content (e.g.,\n   an order retry with a new timestamp) are NOT deduplicated. Use\n   explicit `MessageDeduplicationId` for semantic dedup.\n\n6. **NEVER set visibility timeout lower than the consumer processing\n   time.** If the timeout expires before the consumer deletes the\n   message, the message becomes visible again and may be processed\n   twice. Set the timeout to at least 2x the expected processing time.\n\n7. **NEVER assume high-throughput mode is free.** High-throughput FIFO\n   has a different pricing tier (higher per-request cost), changes\n   deduplication scope from queue-level to group-level, and counts\n   against a separate account quota. Evaluate all three before\n   enabling.\n\n8. **NEVER forget MessageGroupId when sending to a FIFO queue.** Every\n   message sent to a FIFO queue MUST include a `MessageGroupId`.\n   Without it, the API rejects the message.\n\n9. **NEVER convert a Standard queue to FIFO or vice versa.** The\n   queue type (FifoQueue attribute) is IMMUTABLE after creation. To\n   change types, create a new queue and migrate consumers\u002Fproducers.\n\n10. **NEVER assume cross-account delivery works without access policy\n    AND IAM permissions.** Cross-account delivery requires BOTH: (1)\n    the queue access policy grants `sqs:SendMessage` to the producer's\n    account, AND (2) the producer's IAM role allows `sqs:SendMessage`\n    to the queue. Both sides must be configured.\n\n## Output format\n\n```text\nSQS_FIFO: \u003Cqueue-name> (\u003Cqueue-url>)\nVERDICT: READY_TO_DEPLOY | PREREQUISITES_MISSING\nCHECKLIST:\n  [✓|✗] Queue name: \u003Cname>.fifo\n  [✓|✗] FifoQueue: true (immutable)\n  [✓|✗] ContentBasedDeduplication: true | false (explicit dedup ID)\n  [✓|✗] DeduplicationScope: queue | messageGroup\n  [✓|✗] ThroughputLimit: perQueue | messagesPerGroupId\n  [✓|✗] High-throughput mode: enabled (per-group dedup + throughput) | disabled\n  [✓|✗] Message group ID strategy: \u003Cper-entity|single-group> — \u003Cdescription>\n  [✓|✗] Visibility timeout: \u003Cseconds> (consumer processing time estimate: \u003Cseconds>)\n  [✓|✗] DLQ: \u003Cdlq-name>.fifo (\u003Cdlq-arn>) — maxReceiveCount: \u003Ccount> | None\n  [✓|✗] SSE-KMS encryption: enabled (\u003Ckey-arn>) | disabled\n  [✓|✗] Access policy: \u003Csame-account|cross-account> — \u003Cdescription>\n  [✓|✗] Redrive policy: configured (maxReceiveCount=\u003Ccount>) | not configured\n  [✓|✗] Cross-account delivery: enabled (producer accounts: \u003Clist>) | disabled\n  [✓|✗] Tags: \u003Ckey=value list>\nVERIFICATION_COMMANDS:\n  aws sqs get-queue-attributes --queue-url \u003Curl> --attribute-names All\n  aws sqs get-queue-attributes --queue-url \u003Cdlq-url> --attribute-names All\n```\n\n### Worked example — standard FIFO with deduplication, DLQ, and SSE-KMS\n\n```text\nSQS_FIFO: order-processing.fifo (https:\u002F\u002Fsqs.us-east-1.amazonaws.com\u002F123456789012\u002Forder-processing.fifo)\nVERDICT: READY_TO_DEPLOY\nCHECKLIST:\n  [✓] Queue name: order-processing.fifo\n  [✓] FifoQueue: true (immutable)\n  [✓] ContentBasedDeduplication: false (explicit dedup ID)\n  [✓] DeduplicationScope: queue\n  [✓] ThroughputLimit: perQueue\n  [✓] High-throughput mode: disabled\n  [✓] Message group ID strategy: per-entity (customer ID) — per-customer ordering with parallel processing\n  [✓] Visibility timeout: 120 (consumer processing time estimate: 60s)\n  [✓] DLQ: order-processing-dlq.fifo (arn:aws:sqs:us-east-1:123456789012:order-processing-dlq.fifo) — maxReceiveCount: 5\n  [✓] SSE-KMS encryption: enabled (arn:aws:kms:us-east-1:123456789012:key\u002Fabc123)\n  [✓] Access policy: cross-account — producer account 999999999999 granted sqs:SendMessage\n  [✓] Redrive policy: configured (maxReceiveCount=5)\n  [✓] Cross-account delivery: enabled (producer accounts: 999999999999)\n  [✓] Tags: Environment=production, Application=order-service\nVERIFICATION_COMMANDS:\n  aws sqs get-queue-attributes --queue-url https:\u002F\u002Fsqs.us-east-1.amazonaws.com\u002F123456789012\u002Forder-processing.fifo --attribute-names All\n  aws sqs get-queue-attributes --queue-url https:\u002F\u002Fsqs.us-east-1.amazonaws.com\u002F123456789012\u002Forder-processing-dlq.fifo --attribute-names All\n```\n\n## Error handling\n\n→ Moved to [references\u002Ferror-handling.md](references\u002Ferror-handling.md) — symptom → cause → fix for delivery, duplicate processing, throughput, DLQ, and cross-account failures.\n\n## References (load on demand)\n\n- [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) — Mindset (three FIFO misconceptions) and recent AWS features (2023-2026).\n- [references\u002Ferror-handling.md](references\u002Ferror-handling.md) — error-handling deep dive: message delivery, duplicate processing, throughput limits, DLQ attachment, cross-account failures.\n- [references\u002Fdeduplication-and-ordering.md](references\u002Fdeduplication-and-ordering.md) — pre-existing; extended with the message-group-ID partitioning and deduplication-ID management heuristics moved from SKILL.md.\n- [references\u002Fdlq-and-throughput.md](references\u002Fdlq-and-throughput.md) — pre-existing; extended with the high-throughput FIFO quota caveats moved from SKILL.md.\n\n## Domain\n\nAWS CloudOps \u002F Amazon SQS FIFO Queue Provisioning and Message\nOrdering.\n\n## AWS documentation\n\n- **SQS FIFO queues** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAWSSimpleQueueService\u002Flatest\u002FSQSDeveloperGuide\u002Fsqs-fifo-queues.html\n- **Deduplication** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAWSSimpleQueueService\u002Flatest\u002FSQSDeveloperGuide\u002Fusing-messagededuplicationid-property.html\n- **High-throughput FIFO** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAWSSimpleQueueService\u002Flatest\u002FSQSDeveloperGuide\u002Fquotas-queues.html\n- **DLQ and redrive** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAWSSimpleQueueService\u002Flatest\u002FSQSDeveloperGuide\u002Fsqs-dead-letter-queues.html\n- **SSE-KMS** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAWSSimpleQueueService\u002Flatest\u002FSQSDeveloperGuide\u002Fsqs-server-side-encryption.html\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, sqs, fifo, message-queue, cloudops, deploy, provisioning, deduplication, message-group, high-throughput, dlq, redrive, visibility-timeout, sse-kms","1","Jacky Chan — AWS Community Builder","aws-cloudops","AppIntegration","0.1.0","aws, sqs, fifo, message queue, cloudops, deploy, provisioning, deduplication, message group, high throughput, dlq, redrive, visibility timeout, sse kms, cross account","deploy","high","false","capability","Invoke when the user wants to create an SQS FIFO queue, configure message group ID ordering, set up content-based or explicit deduplication, enable high-throughput FIFO mode, attach a dead- letter queue (DLQ), tune visibility timeout, configure SSE-KMS encryption, set up access policies, configure redrive policies, or enable cross-account delivery to a FIFO queue. Do NOT invoke for SQS Standard queues (use standard queue skills), SNS topics, or Amazon MQ.","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 sqs access. Works with Terraform aws_sqs_queue resources and CloudFormation AWS::SQS::Queue templates.","main","eeace51bd5dd1db2030729d83eeab988861553aa","skills\u002Fsqs-fifo-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 sqs-fifo-deployer",{"tool":56,"command":57},"bunx","bunx skills add jhkchan\u002Faws-agent-skills --skill sqs-fifo-deployer",{"tool":59,"command":60},"pnpm","pnpm dlx skills add jhkchan\u002Faws-agent-skills --skill sqs-fifo-deployer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsqs-fifo-deployer\u002FSKILL.md",true,[64,70,74,78,82,86,90,94,98,102,106,110,114,118,122,126,130,134,138],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"eval\u002Ftest-cases.yaml","REFERENCE","参考文档",5779,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsqs-fifo-deployer\u002Feval\u002Ftest-cases.yaml",{"path":71,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":72,"sourceHtmlUrl":73},"evals\u002Fbaselines\u002Fcross-account-fifo-delivery.md",581,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsqs-fifo-deployer\u002Fevals\u002Fbaselines\u002Fcross-account-fifo-delivery.md",{"path":75,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":76,"sourceHtmlUrl":77},"evals\u002Fbaselines\u002Fhigh-throughput-fifo-partitioning.md",596,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsqs-fifo-deployer\u002Fevals\u002Fbaselines\u002Fhigh-throughput-fifo-partitioning.md",{"path":79,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":80,"sourceHtmlUrl":81},"evals\u002Fbaselines\u002Fmissing-deduplication-config.md",522,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsqs-fifo-deployer\u002Fevals\u002Fbaselines\u002Fmissing-deduplication-config.md",{"path":83,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":84,"sourceHtmlUrl":85},"evals\u002Fbaselines\u002Fmissing-fifo-attribute.md",466,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsqs-fifo-deployer\u002Fevals\u002Fbaselines\u002Fmissing-fifo-attribute.md",{"path":87,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":88,"sourceHtmlUrl":89},"evals\u002Fbaselines\u002Fstandard-fifo-with-dedup-and-dlq.md",653,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsqs-fifo-deployer\u002Fevals\u002Fbaselines\u002Fstandard-fifo-with-dedup-and-dlq.md",{"path":91,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":92,"sourceHtmlUrl":93},"evals\u002Feval_config.yaml",1837,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsqs-fifo-deployer\u002Fevals\u002Feval_config.yaml",{"path":95,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":96,"sourceHtmlUrl":97},"evals\u002Fevals.json",8918,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsqs-fifo-deployer\u002Fevals\u002Fevals.json",{"path":99,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":100,"sourceHtmlUrl":101},"evals\u002Fprompts\u002Fcross-account-fifo-delivery.md",619,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsqs-fifo-deployer\u002Fevals\u002Fprompts\u002Fcross-account-fifo-delivery.md",{"path":103,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":104,"sourceHtmlUrl":105},"evals\u002Fprompts\u002Fhigh-throughput-fifo-partitioning.md",592,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsqs-fifo-deployer\u002Fevals\u002Fprompts\u002Fhigh-throughput-fifo-partitioning.md",{"path":107,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":108,"sourceHtmlUrl":109},"evals\u002Fprompts\u002Fmissing-deduplication-config.md",412,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsqs-fifo-deployer\u002Fevals\u002Fprompts\u002Fmissing-deduplication-config.md",{"path":111,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":112,"sourceHtmlUrl":113},"evals\u002Fprompts\u002Fmissing-fifo-attribute.md",366,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsqs-fifo-deployer\u002Fevals\u002Fprompts\u002Fmissing-fifo-attribute.md",{"path":115,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":116,"sourceHtmlUrl":117},"evals\u002Fprompts\u002Fstandard-fifo-with-dedup-and-dlq.md",601,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsqs-fifo-deployer\u002Fevals\u002Fprompts\u002Fstandard-fifo-with-dedup-and-dlq.md",{"path":119,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":120,"sourceHtmlUrl":121},"examples\u002FREADME.md",5982,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsqs-fifo-deployer\u002Fexamples\u002FREADME.md",{"path":123,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":124,"sourceHtmlUrl":125},"references\u002Fadvanced-patterns.md",3884,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsqs-fifo-deployer\u002Freferences\u002Fadvanced-patterns.md",{"path":127,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":128,"sourceHtmlUrl":129},"references\u002Fdeduplication-and-ordering.md",12152,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsqs-fifo-deployer\u002Freferences\u002Fdeduplication-and-ordering.md",{"path":131,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":132,"sourceHtmlUrl":133},"references\u002Fdlq-and-throughput.md",9892,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsqs-fifo-deployer\u002Freferences\u002Fdlq-and-throughput.md",{"path":135,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":136,"sourceHtmlUrl":137},"references\u002Ferror-handling.md",1022,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsqs-fifo-deployer\u002Freferences\u002Ferror-handling.md",{"path":139,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":140,"sourceHtmlUrl":141},"skill.usf.yaml",4251,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsqs-fifo-deployer\u002Fskill.usf.yaml",[143,150,157,164,171,178],{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":149,"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":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":156,"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":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":163,"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":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":170,"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":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":177,"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":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":184,"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",[],[]]