Skip to content

fix: disable EC2 detailed monitoring on Kafka, ClickHouse, Cassandra,… - #267

Open
jkondrat-sd wants to merge 1 commit into
juspay:mainfrom
jkondrat-sd:improve-cost-efficiency
Open

fix: disable EC2 detailed monitoring on Kafka, ClickHouse, Cassandra,…#267
jkondrat-sd wants to merge 1 commit into
juspay:mainfrom
jkondrat-sd:improve-cost-efficiency

Conversation

@jkondrat-sd

Copy link
Copy Markdown

Addresses findings from the InfraScan cost analysis report:
https://infrascan.soldevelo.com/report/hyperswitch-suite-254c5531-0923-48c0-9252-1780283139df

Changes:

  • EC2 Detailed Monitoring - Set monitoring = false on 7 instances across 5 modules (kafka, clickhouse, cassandra, locker, jump-host). Detailed 1-minute CloudWatch metrics cost around $2-3/month per instance; standard 5-minute monitoring remains active. Combined saving: around $14-21/month.

Not addressed (require maintainer review):

  • Expensive NAT Gateway - NAT gateway in modules/base/subnet. Likely needed for private subnet egress; removal is an architectural decision.
  • Load Balancer for Single Instance (5 findings) - ALBs and NLBs across nlb, alb, load-balancer, clickhouse, and locker modules. Each serves an active service; fixed cost around $15-25/month each.
  • API Gateway REST Instead of HTTP API - REST API in modules/base/api-gateway. Migrating to HTTP API requires code changes to callers.
  • Missing Cost and Usage Report / Missing AWS Budget (26 findings each) - Organisation-level governance, not addressable at the module level.

Related: #264

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants