Real AWS Costs

Estimating What the Same Stack Would Cost on Real AWS

Every service in the stack bills by use. The table uses AWS 24 's on-demand prices for US East (N. Virginia) on 26 September 2026 (not run here), for a million page views a month, each loading two S3 24 files and one 100 ms API call:

BookNest's stack priced on AWS, us-east-1, September 2026
Item Price BookNest, 1M views a month
Lambda 24 requests $0.20 per million, first million free $0.00
Lambda duration $0.0000166667 per GB-second, 400,000 free $0.00 (25,000 GB-s)
DynamoDB 24 on-demand reads $0.125 per million read units at most $0.13
DynamoDB storage, PITR $0.25 and $0.20 per GB-month, 25 GB free $0.00
S3 Standard GET requests $0.0004 per 1,000 $0.80
VPC, gateway endpoint; data out free; 100 GB free, then $0.09/GB $0.00
NAT gateway (not used) $0.045 per hour plus $0.045 per GB would add $32.85

Under a dollar a month, and the Lambda and DynamoDB storage allowances are always free; new accounts also get $100 in credits (up to $100 more for activities), and a Free-plan account closes after six months or when they run out. A NAT gateway would cost thirty times the rest, hence the gateway endpoint; API Gateway 24 's REST API would add $3.50 per million calls, while a function URL adds nothing beyond the invocation.

Two tools watch real spending (not run here: 4.13.1 answers budgets calls with "not currently supported" and has no Cost Explorer). AWS Budgets alerts when actual or forecast spending crosses a threshold; monitoring is free, as are the first two budgets with actions, then $0.10 a day each. Cost allocation tags split the bill: CloudFormation 24 propagates the stack's --tags app=booknest to every taggable resource, and once app is activated in the Billing console (up to 24 hours), Cost Explorer and budgets can filter on it. LocalStack 63,725 does not propagate stack tags; the table, function and bucket came back untagged.