mirror of
https://github.com/EddieTheCubeHead/Stagnum.git
synced 2026-04-26 06:05:49 +03:00
[GH-ISSUE #336] [Infra]: Cost optimizing AWS #193
Labels
No labels
bug
bug
client
design
documentation
feature
feature
infrastructure
pull-request
ready for development
server
server
spike
technical work
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Stagnum#193
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ekosfin on GitHub (Jun 13, 2024).
Original GitHub issue: https://github.com/EddieTheCubeHead/Stagnum/issues/336
Originally assigned to: @ekosfin on GitHub.
Contact details
No response
Addressed problem
Currently InfraCost estimates the monthly cost to be 75$. For the usage of this project that is not reasonable cost.
Feature description
As things stand using ECS is costing roughly 20$ for both front and backend. However, the terraform is configured such that both have their own application load balancers (ALB) that cost 20$ each. I would recommend, just forgoing ECS and moving the infra to one EC2 instance. This will be more prone to downtime as the whole infra would be reliant on one availability zone, however considering the lack of criticality this seems like a good trade off. I estimate the cost to go down to 10-20$ with this architecture.
Alternative solutions
The ECS could be also configured to use one ALB instead of two. This would bring the cost down to roughly 55$
Additional information
No response