AWS cost estimate (26.4) vs. the aws-cost app — analysis for #221 - #222
Open
kyle-lesinger wants to merge 1 commit into
Open
AWS cost estimate (26.4) vs. the aws-cost app — analysis for #221#222kyle-lesinger wants to merge 1 commit into
kyle-lesinger wants to merge 1 commit into
Conversation
Analysis for #221 — parse the 'Disasters API and Infra Cost Estimates 26.4' sheet (APIs/RDS/SM2A/Cumulative) and compare cell-by-cell to cost-dashboard's On-Demand model + us-west-2 pricing snapshot. - Agree: db.t3.small and db.r5.large match exactly (bare On-Demand, x730). - Diverge: db.t4g.medium $138.92 vs $47.45 (Multi-AZ/storage bundled); Lambda API $ ~8-25x app (memory not captured + likely API Gateway/rounding); ECS (the bulk of SM2A) has no app service. - Future work: ECS/Fargate, RDS Multi-AZ, API Gateway + Lambda memory, and lightweight estimated line items (CloudFront/Amplify/Secrets Manager).
✅ Deploy Preview for veda-pr-dashboard canceled.
|
✅ Deploy Preview for veda-github-actions canceled.
|
✅ Deploy Preview for veda-leave-dashboard canceled.
|
✅ Deploy Preview for veda-dse-hub canceled.
|
✅ Deploy Preview for veda-aws-dashboard canceled.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Relates to #221 (AWS Cost Estimate from Alexandra).
Adds
docs/COST_ESTIMATE_COMPARISON.md: a cell-by-cell comparison of the Disasters API and Infra Cost Estimates 26.4 sheet (linked in #221) against thecost-dashboard/On-Demand model + theus-west-2pricing snapshot.What the analysis found
Agree where they overlap (On-Demand, ×730 h/mo):
db.t3.smalldb.r5.largeThree major divergences:
db.t4g.medium— sheet $138.92 vs app $47.45 (~2.9×). The SM2A "airflow db" figure bundles Multi-AZ/storage; the app prices bare instance-hours + itemizes storage. Also internally inconsistent with the sheet's other (bare-rate) RDS rows.Structural: the sheet does dataset-scaling, named what-if rollups, and cost-allocation heuristics ("2/3 of ECS", untagged) that the generic calculator doesn't.
Implications
Future work
Full write-up, tables, and file/line references are in the doc.