Skip to content
allanninal.dev/build
Collaborate

Part 6 of 7 · Data request handler series ~5 min read

What the data request handler costs

The cost here is screening inbound mail rather than handling requests, because requests are rare and messages are not. Eight thousand messages a month is a busy small-business inbox. Here is where each cent goes.

Key takeaways

  • About $18 a month at 8,000 messages. Roughly $65 at 30,000 messages.
  • One Bedrock read per message screened is the only line that scales. Everything else is rounding.
  • Nothing is always-on, so a quiet month genuinely costs almost nothing.
  • Cheap filters remove auto-replies and bulk mail before any model call, which is most of the volume.
  • The duplicate test runs before the read, so resends are free.
  • The three real risks: a retry loop, storage nobody expires, and a bigger model than the job needs.

The bill at three volumes

These are US East prices at the time of writing, at three volumes that bracket most small businesses. Find the bar closest to your own and read across.

Monthly cost of the data request handler at three volumesA stacked bar chart with three bars, one per volume tier: 2,000 messages totalling about $5, 8,000 messages totalling about $18, and 30,000 messages totalling about $65. Each bar is stacked from bands. The largest and fastest-growing is Bedrock, one read per message screened, in teal. Then SES for the messages, in pink. Then S3 and DynamoDB storage in green. Then a fixed orange band for Secrets Manager and AWS Budgets, which is eighty-six cents at every volume. Then a grey band for Lambda, SQS and CloudWatch. A note says the read is the only bar that grows with the business and the orange band never moves.$0$20$40$60$80~$5.462,000 messages~$18.148,000 messages~$64.630,000 messagesBedrock — one read per message screenedSES — asks, results, receiptsS3 + DynamoDBFixed — Secrets Manager, BudgetsLambda, SQS, CloudWatchThe read is the only bar that grows with the business. The orange fixed band never moves.
Fig 1. The monthly bill at three volumes. The teal band — one model read per message screened — is the only part that grows; the orange fixed band is the same 86 cents at every volume.

Line by line

LineAt 8,000 messagesHow it scales
Bedrock read$4.80Linear. One call per message screened, roughly 1,800 in and 200 out tokens.
SES$4.02Linear. About 0.02 messages per message screened.
DynamoDB + S3$1.56Storage grows with what you retain, not with throughput.
Lambda + SQS$0.12Linear, and effectively free at this scale.
CloudWatch$0.16Flat, if you set retention. Unbounded if you do not.
Secrets Manager$0.40Flat. One secret, $0.40 a month.
AWS Budgets$0.46Flat. Two actions, so you find out before the bill does.

The read cost is one short model call per message that survives the cheap filters, which is a minority of an inbox. Handling an actual request costs almost nothing because there are so few of them.

The three ways this bill surprises you

Every one of these has happened to somebody, and all three are cheap to prevent.

  • Screening every message with a model. Auto-replies, bulk mail and internal threads are a large fraction of an inbox and can be excluded structurally for nothing.
  • Storing gathered packages indefinitely. A package contains everything you hold about a person, which is the last thing to keep a spare copy of. Delete it a set period after the response is sent.
  • Log retention left at never. Logs from a system that reads inbound mail are exactly the logs you least want kept forever, quite apart from the cost.

What it costs when nothing happens

This matters more than the headline number for a seasonal business. In a month with nothing to process the bill is the fixed band: Secrets Manager at forty cents, AWS Budgets at forty-six, and a few cents of storage. Call it a dollar. There is no instance to stop and nothing to remember to turn off.

The monthly bill at four volumes plus one failure modeA horizontal row of five boxes. Quiet month, about one dollar. 2,000 messages, about $5. 8,000 messages, about $18. 30,000 messages, about $65. And one bad retry loop, about two hundred dollars. A note says four of these are the design working and the fifth is a missing dead-letter queue.THE BILL, AT A GLANCEQuiet month~$12,000 messages~$58,000 messages~$1830,000 messages~$65One bad loop~$200Four of these are the design working. The fifth is a missing dead-letter queue.
Fig 2. The bill at a glance, including the one that is not a volume at all. A retry loop with no dead-letter queue costs more than every legitimate use of the system put together.
  • Management
  • Analytics
  • Front-end & mobile

Set these on day one

  • A dead-letter queue on every SQS queue, with a maximum receive count of three.
  • Thirty-day retention on every CloudWatch log group. There is no default that is safe.
  • An S3 lifecycle rule on the object prefix, tiering at 90 days and expiring at your actual record-keeping horizon.
  • Two AWS Budgets actions — one that emails at half your expected spend, one at double it. The second is how you find out about a loop in an hour instead of a month.
  • Provisioned concurrency: none. Nothing here is latency-sensitive enough to justify paying for a warm function.

Next: the same system drawn for engineers — service names, resource identifiers, IAM scopes, table schemas and the model id.

All posts