Cost-Optimized EC2 Instance Strategy for Logwise Integration

[Priyanshuuttam]

Team, regarding the instance requirements—as discussed—I found that the best-fit ARM64 (Graviton) instance for running Logwise with minimal cost is c7g.2xlarge (8 vCPU, 16 GB RAM) with 100 GB gp3 EBS.

The estimated cost comes to around ₹13,000/month i wanted to check if we can start with c7g.xlarge (4 vCPU, 8 GB RAM), since our platform currently doesn’t have high WPS.

Would this impact Logwise in any way? We can always scale up the instance later if capacity requirements increase, which would help optimize costs for now.

[onkar-dream11]

It shouldn’t negatively impact Logwise to start with c7g.xlarge (4 vCPU, 8 GB RAM) given the current low WPS.

Based on our testing so far, even with 4 vCPU and 8 GB RAM, the system is able to comfortably handle ~3–4 MBps ingestion, with CPU utilization staying around 30–40%. So from a compute perspective, this configuration is sufficient for the current load, and scaling up later is straightforward if throughput increases.

One important thing to ensure, however, is storage. Please make sure we provision at least 100 GB gp3 EBS. Kafka has a default retention of 1 hour, and depending on the incoming log volume, data will accumulate quickly on disk. Storage tends to be the first bottleneck before CPU or memory in such setups.

In summary:

• c7g.xlarge is fine for now and won’t impact Logwise performance at current load
• Ensure 100 GB EBS to safely handle Kafka retention and bursty ingestion
• We can scale up the instance later if/when capacity requirements grow

Starting smaller makes sense from a cost-optimization standpoint.