| Item | Unit price | Monthly 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 | — |
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.
| Component | Monthly | This week |
|---|---|---|
| Staging server, t4g.medium | 24.53 | 5.67 |
| Application server, t4g.small | 12.26 | 2.83 |
| EBS 40 GB gp3 | 3.20 | 0.74 |
| CloudWatch, 10 GB ingested | 5.00 | 1.15 |
| Snapshots, 20 GB | 1.00 | 0.23 |
| S3 5 GB plus writes | 0.60 | 0.14 |
| Route 53 zone and queries | 0.60 | 0.14 |
| SES, 200 emails | 0.02 | — |
| Week 0 | 47.21 | 10.90 |
Previously stated: $45. Correct figure: $10.90. The $45 was the monthly cost of that stack.
Full stack live but light traffic. Four weeks is 0.924 of a month.
| Component | Monthly | 4 weeks |
|---|---|---|
| Two c7g.large application servers, one per zone | 105.86 | 97.81 |
| Worker, t4g.small | 12.26 | 11.33 |
| Load balancer, base plus light LCU | 20.00 | 18.48 |
| WAF, webACL plus four rules | 9.00 | 8.32 |
| CloudWatch, 20 GB ingested | 10.00 | 9.24 |
| S3 storage and writes | 2.00 | 1.85 |
| CloudFront, 15 GB egress | 1.28 | 1.18 |
| Snapshots, 40 GB | 2.00 | 1.85 |
| SES 3,000 emails, Route 53, SQS | 1.10 | 1.02 |
| Weeks 1 to 4 | 163.50 | 151.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.
Eight weeks of steady state, with one election-day spike using autoscaling for six hours plus the egress and logging that spike carries.
| Component | Steady, 8 weeks | Spike, once | Total |
|---|---|---|---|
| Application and worker, steady | 109.05 | — | 109.05 |
| Autoscaling, four extra c7g.large for six hours | — | 1.74 | 1.74 |
| Load balancer and LCU | 18.48 | 0.90 | 19.38 |
| WAF | 8.32 | 0.40 | 8.72 |
| CloudWatch, steady plus burst | 9.24 | 12.00 | 21.24 |
| S3, photographs accumulating to 60 GB | 3.80 | 2.20 | 6.00 |
| CloudFront, 40 GB steady plus 200 GB spike day | 3.40 | 17.00 | 20.40 |
| Snapshots, 30-day retention to 100 GB | 3.70 | — | 3.70 |
| SES 20,000 emails, Route 53, SQS | 4.10 | — | 4.10 |
| Weeks 5 to 12 | 160.09 | 34.24 | 194.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.
| Component | USD |
|---|---|
| Final export, 60 GB written to S3 | 1.38 |
| Export download, 60 GB egress | 5.40 |
| Three days of stack running while the export is verified | 16.10 |
| Snapshot retained for 30 days after teardown | 5.00 |
| Decommission | 27.88 |
Previously stated: $25. Correct figure: $27.88. This row was right.
| Period | Weeks | USD |
|---|---|---|
| Week 0, build | 1 | 10.90 |
| Weeks 1 to 4, build and pilot | 4 | 151.08 |
| Weeks 5 to 12, campaign window with election day | 8 | 194.33 |
| Decommission and final export | — | 27.88 |
| Total, 13 weeks | 13 | 384.19 |
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.
| Scenario | 13-week AWS total |
|---|---|
| Campaign stack only, offers 1 to 3 | 384 |
| Campaign stack plus polling at state-pilot scale, 8 weeks at $220 a month | 790 |
| Campaign stack plus national polling steady, 8 weeks at $759 a month | 1,786 |
| Campaign stack plus national polling including election day, 8 weeks at $1,018 a month | 2,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.
| Point for Samantha | Detail |
|---|---|
| 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 accumulates | Engineer-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 number | Photograph 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