Skip to content

anyshift-io/sre-skills / skills/sqs-queue-auditor

sqs-queue-auditor

Verified

FileKindSize
FAILURE_MODES.mdmarkdown6.6 KB
README.mdmarkdown4.9 KB
SKILL.mdskill md13.3 KB
examples/01-no-dlq.mdmarkdown2.9 KB
examples/02-dlq-retention-shorter-than-source.mdmarkdown3.3 KB
examples/03-maxreceivecount-too-low.mdmarkdown2.8 KB
examples/04-poison-ages-out-before-dlq.mdmarkdown3.9 KB
examples/05-default-visibility-short-retention.mdmarkdown3.2 KB
examples/06-public-queue-policy.mdmarkdown3.6 KB
examples/07-fifo-dedup-off.mdmarkdown2.8 KB
examples/08-clean-standard.mdmarkdown2.6 KB
fixtures/01-no-dlq/queue.jsonconfig564 B
fixtures/02-dlq-retention-shorter-than-source/dlq.jsonconfig649 B
fixtures/02-dlq-retention-shorter-than-source/queue.jsonconfig632 B
fixtures/03-maxreceivecount-too-low/dlq.jsonconfig659 B
fixtures/03-maxreceivecount-too-low/queue.jsonconfig637 B
fixtures/04-poison-ages-out-before-dlq/dlq.jsonconfig663 B
fixtures/04-poison-ages-out-before-dlq/queue.jsonconfig648 B
fixtures/05-default-visibility-short-retention/dlq.jsonconfig650 B
fixtures/05-default-visibility-short-retention/queue.jsonconfig631 B
fixtures/06-public-queue-policy/dlq.jsonconfig663 B
fixtures/06-public-queue-policy/queue.jsonconfig908 B
fixtures/07-fifo-dedup-off/dlq.jsonconfig748 B
fixtures/07-fifo-dedup-off/queue.jsonconfig804 B
fixtures/08-clean-standard/dlq.jsonconfig672 B
fixtures/08-clean-standard/queue.jsonconfig1.0 KB
tests/README.mdmarkdown4.2 KB
tests/_audit.pyscript21.8 KB
tests/_replay.pyscript720 B
tests/eval/README.mdmarkdown8.4 KB
tests/eval/eval_results.jsonconfig220.4 KB
tests/eval/judge_prompt.mdmarkdown1.4 KB
tests/eval/queues.pyscript7.6 KB
tests/eval/rubric.mdmarkdown2.6 KB
tests/eval/run_eval.pyscript11.5 KB
tests/replay_01_no_dlq.pyscript1.5 KB
tests/replay_02_dlq_retention.pyscript1.5 KB
tests/replay_03_maxreceivecount.pyscript1.3 KB
tests/replay_04_poison_ages_out.pyscript1.6 KB
tests/replay_05_default_visibility.pyscript1.8 KB
tests/replay_06_public_policy.pyscript1.4 KB
tests/replay_07_fifo_dedup_off.pyscript1.4 KB
tests/replay_08_clean_standard.pyscript1.6 KB

examples/08-clean-standard.md

View on GitHub
# Worked example 8: a clean queue (control)

A correctly-configured queue. The audit produces zero findings, does not invent one, and still reports its boundary. This control is what keeps the skill trustworthy: an auditor that flags clean configs is one operators learn to ignore. Fixtures and replay test under `../fixtures/08-clean-standard/` and `../tests/replay_08_clean_standard.py`.

## Scenario

- **Queue**: `notification-fanout`, with DLQ `notification-fanout-dlq`. Subscribed to an SNS topic, processed by a worker fleet.

## Step 1: parse the attributes

```
VisibilityTimeout      180      (deliberate, not the 30s default)
MessageRetentionPeriod 345600   (4 days)
SqsManagedSseEnabled   true
Policy                 Allow Principal:"*" SendMessage,
                       Condition ArnEquals aws:SourceArn = ...:sns:account-events
RedrivePolicy          {"deadLetterTargetArn":"...:notification-fanout-dlq","maxReceiveCount":5}
```
DLQ (`dlq.json`):
```
MessageRetentionPeriod 1209600  (14 days)
```

## Steps 2-5: every check passes

- **Redrive (R1/R2/R3)**: DLQ present; `maxReceiveCount=5` in band; DLQ retention (14 days) is longer than the source (4 days). Clean.
- **Lifecycle (R4/R5/R6)**: `5 x 180 = 900s`, far under the 4-day retention, so poison messages reach the DLQ with room to spare. Visibility is a deliberate 180s, not the default. Retention is the 4-day default. Clean.
- **Exposure (R7/R8)**: the resource policy uses `Principal: "*"` **but narrows it** with `aws:SourceArn` pinned to the SNS topic. This is the standard, correct SNS-to-SQS pattern, so R7 does **not** fire. SSE is on, so R8 does not fire. Clean.
- **FIFO (R9)**: standard queue, not FIFO. Not applicable.

No findings.

## Boundary

A clean configuration is not a clean system. Even here, the audit reports what it cannot see:

- The queue could still be failing right now (a crashing consumer, a producer that stopped) for a reason only the live metrics show. Join: queue to its metrics over time.
- The effective access is still the union of this scoped resource policy and the account's identity policies. Join: queue to the account's IAM graph.
- Whether anyone is draining the DLQ is still unknown. Join: DLQ to its owner.

## Why this is the control

It pins two behaviours the other seven examples cannot: that the skill produces **zero** findings on a correct queue (no false positives), and specifically that a wildcard principal scoped by `aws:SourceArn` is recognised as legitimate and not flagged as R7. It also makes the boundary point unmissable: the audit reports the join it cannot make even when there is nothing to fix, because a sound config and a healthy system are different claims.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall