← Reports

AWS life of engagement — the actual breakdown

GBAJA 27 · 1 November 2026, 23:35 SGT · Elena, Chief Technology · supersedes the schedule table in the feasibility review
The error, named. In the published schedule I put monthly dollar figures into weekly rows and then multiplied by weeks. "Week 0 — $45" is a monthly cost for a small stack, not a week of it. "Weeks 1-4 — $150 each" and "Weeks 5-12 — $175 each" are monthly figures used as weekly ones. Multiply by four and a quarter and the total comes out about 3.3 times too high. The $2,070 total is wrong, and my "correction" from $450 to $2,070 made it worse rather than better. Below is the same engagement derived properly, line by line, at on-demand prices.

Price inputs used

ItemUnit priceMonthly at 730 hours
c7g.large, application server$0.0725 / hour$52.93
t4g.small, worker or staging$0.0168 / hour$12.26
t4g.medium, staging$0.0336 / hour$24.53
Application load balancer$0.0225 / hour + LCU$16.43 + LCU
EBS gp3$0.08 / GB-month—
EBS snapshot$0.05 / GB-month—
S3 standard, storage and PUT$0.023 / GB, $0.005 / 1k PUT—
CloudFront egress$0.085 / GB—
CloudWatch logs$0.50 / GB ingested—
WAF$5 webACL + $1 / rule + $0.60 / M requests—
SES, Route 53$0.10 / 1k emails, $0.50 / zone—

Week 0 — build week

One staging box, one small application box, no CDN traffic, no load balancer yet. Seven days, so a monthly price is divided by 4.33 to get the week.

ComponentMonthlyThis week
Staging server, t4g.medium24.535.67
Application server, t4g.small12.262.83
EBS 40 GB gp33.200.74
CloudWatch, 10 GB ingested5.001.15
Snapshots, 20 GB1.000.23
S3 5 GB plus writes0.600.14
Route 53 zone and queries0.600.14
SES, 200 emails0.02—
Week 047.2110.90

Previously stated: $45. Correct figure: $10.90. The $45 was the monthly cost of that stack.

Weeks 1 to 4 — build and pilot

Full stack live but light traffic. Four weeks is 0.924 of a month.

ComponentMonthly4 weeks
Two c7g.large application servers, one per zone105.8697.81
Worker, t4g.small12.2611.33
Load balancer, base plus light LCU20.0018.48
WAF, webACL plus four rules9.008.32
CloudWatch, 20 GB ingested10.009.24
S3 storage and writes2.001.85
CloudFront, 15 GB egress1.281.18
Snapshots, 40 GB2.001.85
SES 3,000 emails, Route 53, SQS1.101.02
Weeks 1 to 4163.50151.08

Previously stated: 4 × $150 = $600. Correct figure: $151. The $163.50 monthly figure is the "full stack" number; it was never a weekly figure.

Weeks 5 to 12 — campaign window to 16 January

Eight weeks of steady state, with one election-day spike using autoscaling for six hours plus the egress and logging that spike carries.

ComponentSteady, 8 weeksSpike, onceTotal
Application and worker, steady109.05—109.05
Autoscaling, four extra c7g.large for six hours—1.741.74
Load balancer and LCU18.480.9019.38
WAF8.320.408.72
CloudWatch, steady plus burst9.2412.0021.24
S3, photographs accumulating to 60 GB3.802.206.00
CloudFront, 40 GB steady plus 200 GB spike day3.4017.0020.40
Snapshots, 30-day retention to 100 GB3.70—3.70
SES 20,000 emails, Route 53, SQS4.10—4.10
Weeks 5 to 12160.0934.24194.33

Previously stated: 8 × $175 = $1,400. Correct figure: $194. The election-day spike, in real money, is $34, not the $125 I implied. Autoscaling for a day is cheap; what costs money on election day is the images and the egress, and both are small at these volumes.

Decommission

ComponentUSD
Final export, 60 GB written to S31.38
Export download, 60 GB egress5.40
Three days of stack running while the export is verified16.10
Snapshot retained for 30 days after teardown5.00
Decommission27.88

Previously stated: $25. Correct figure: $27.88. This row was right.

Corrected total, campaign stack only

PeriodWeeksUSD
Week 0, build110.90
Weeks 1 to 4, build and pilot4151.08
Weeks 5 to 12, campaign window with election day8194.33
Decommission and final export—27.88
Total, 13 weeks13384.19
$384, not $2,070. The original $450 was close. This figure is slightly under it because that estimate assumed heavier logging and a managed database throughout; the stack here is self-hosted until it needs otherwise. For a pitch, state about $400 of AWS across the whole engagement, or roughly $30 a week, and add a 20% contingency if you want to be safe against a bad traffic day.

Where $2,070 was actually coming from

The number is not meaningless, it belongs to a different scenario: the campaign stack plus the national polling stack running in the same account for the last eight weeks. That stack is genuinely an order of magnitude larger.

Scenario13-week AWS total
Campaign stack only, offers 1 to 3384
Campaign stack plus polling at state-pilot scale, 8 weeks at $220 a month790
Campaign stack plus national polling steady, 8 weeks at $759 a month1,786
Campaign stack plus national polling including election day, 8 weeks at $1,018 a month2,264

So $2,070 is a defensible number only when national polling runs alongside the campaign. It was never the campaign stack alone, and I should have labelled it that way instead of presenting it as a correction.

What this does to the pricing conversation

Point for SamanthaDetail
AWS is immaterial to price$384 across an engagement quoted at $20,400 to $186,400. Infrastructure is under 1% of the ticket in the smallest offer and under 2% in the largest. Price on engineering and on the value of the evidence, never on hosting.
The only infrastructure number worth quoting to a client"Under $500 of cloud across the engagement, included in the platform fee." Anything larger invites a conversation about our efficiency.
Where cost actually accumulatesEngineer-days, then hardware for offer 3, then field training and travel. In that order. AWS does not appear in the top five at any offer.
The risk that changes the numberPhotograph volume and retention, not compute. If the client insists images are kept indefinitely at full resolution, egress and storage quadruple; still under $2,000, but state the retention policy in the contract.

Elena · Chief Technology · 1 November 2026, 23:35 SGT · every unit price above is the published on-demand rate for us-east-2 style pricing in us-east-1, rounded; hours at 730 per month and 4.33 weeks per month · supersedes the schedule table in the feasibility review of the same date