Skip to content
allanninal.dev/build
Collaborate

Part 6 of 7 · Packaging data reporter series ~5 min read

What the packaging data reporter costs

The model reads packaging specifications, and those arrive when the range changes or when a supplier finally answers. Everything per unit, per sales line and per month is arithmetic. A hundred and eighty specifications a month is a business actively clearing its estimate backlog. Here is where each cent goes.

Key takeaways

  • About $3 a month at 180 specs a month. Roughly $6 at 600 specs a month.
  • One Bedrock read per specification is the only line that scales. Everything else is rounding.
  • Nothing is always-on, so a quiet month genuinely costs almost nothing.
  • Storage is the line that grows here, because seven years of evidence is the point of the system rather than a side effect.
  • 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 packaging data reporter at three volumesA stacked bar chart with three bars, one per volume tier: 40 specs a month totalling about $2, 180 specs a month totalling about $3, and 600 specs a month totalling about $6. Each bar is stacked from bands. The largest and fastest-growing is Bedrock, one read per specification, 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$2$4$6$8~$1.5940 specs a month~$2.75180 specs a month~$6.24600 specs a monthBedrock — one read per specificationSES — 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 specification — is the only part that grows; the orange fixed band is the same 86 cents at every volume.

Line by line

LineAt 180 specs a monthHow it scales
Bedrock read$1.08Linear. One call per specification, roughly 1,800 in and 200 out tokens.
SES$0.12Linear. About 1.5 messages per specification.
DynamoDB + S3$0.44Storage 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.

Roughly one model call per packaging specification, against a mid-tier model. A spec sheet is a short document with a material, a weight and a component, sometimes in a table and sometimes in a sentence in an email. That is extraction with awkward formatting, which is not the same as difficulty, and a frontier model reads the same three fields for several times the price.

The three ways this bill surprises you

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

  • Running a model over the sales export. It is millions of fixed-header rows and it is by far the largest file in the system. Parse it; a model over it would cost more than the fees it is calculating.
  • Re-reading every specification at every period close. A spec is read when it arrives and re-read when it is superseded. Twice a year is not an event that should touch the model at all.
  • Never expiring the raw sales imports. The derived tonnage and its links must survive seven years. The hundred-million-row monthly export behind it does not, once it has been aggregated and reconciled.

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. 40 specs a month, about $2. 180 specs a month, about $3. 600 specs a month, about $6. 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~$140 specs a month~$2180 specs a month~$3600 specs a month~$6One 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