Most cloud cost guides are written for a company already spending six figures a month, with a FinOps team and a Savings Plans strategy. That is not a ten-person, pre-Series-A startup in Bengaluru or Chennai running an AWS bill under Rs 5 lakh a month. At that size the bill is small enough that nobody has made it anyone's job, and large enough that a founder notices it every month on the P&L. The fixes are different too: cheaper to find, faster to apply, and mostly invisible to a generic checklist written for AWS's biggest customers.
This is not the general AWS cost-cutting guide
We already have a general playbook on cutting AWS bills that covers Cost Explorer, tagging, and the broad mechanics of compute, storage, and data transfer. This post does not repeat that ground. It is narrower on purpose: what changes for an Indian seed-stage company specifically, where the bill is small, the account is often less than a year old, and the INR invoice comes with quirks the US-focused guides never mention.
The India billing reality nobody explains upfront
If your AWS contact and billing address is in India, your agreement is with Amazon Web Services India Private Limited, a local AWS seller, and your invoice total is listed in INR instead of USD. That single fact changes three things that catch founders out:
- GST applies, and you can claim it back. Tax invoices carry your PAN if you add it during setup, which is what your accountant needs to treat the GST component as an input tax credit rather than a sunk cost. Skipping the PAN step is a common miss that means redoing paperwork later.
- Card verification charges, then refunds, 2 INR. A tiny, real detail: AWS India charges your card 2 INR during signup verification and refunds it once verification completes. Harmless, but it is the first sign your account is on the India entity rather than the global one, which matters for every other billing decision below.
- Startup credits change currency and tier by program. AWS Activate has two founder-facing tiers as published on AWS's own startups page: a self-funded "Founders" tier of up to $5,000 (starting at $1,000), and a "Portfolio" tier of up to $200,000 for startups backed by a participating accelerator, VC, or startup platform. Both are issued and tracked in USD even on an India-billed account. Apply for whichever tier you qualify for before you optimize anything else. Free money should be claimed before you spend engineering hours chasing a smaller saving.
The cost levers, in the order that actually moves a sub-Rs 5L bill
At this size, order of operations matters more than the individual technique. Committed-use discounts are the first thing most cost articles lead with, and the last thing a seed-stage account should touch, because they lock in a shape of spend before you know what your infrastructure will look like in six months. Here is the order that actually reduces a small bill without creating a new problem.
1. Kill graveyard resources first, because it is free money
Before touching a single running service, find what is running for no reason. This is the highest-leverage move at seed stage because the fix costs zero risk: nothing depends on a resource nobody is using.
- Unattached EBS volumes:
aws ec2 describe-volumes --filters Name=status,Values=available lists every volume billing you with nothing attached to it.
- Old manual and automated RDS snapshots piling up past what you need for recovery.
- Elastic IPs reserved but not attached to a running instance (AWS bills unattached EIPs by the hour).
- Load balancers left pointing at a service that was decommissioned months ago.
- Dev and staging environments that scale on weekdays and keep running, unscaled, every weekend and holiday.
Nobody publishes a reliable industry-wide percentage for how much of a small account this represents, and treat any number you see quoted for "typical waste" as marketing rather than fact for your account specifically. The only honest answer is: run the audit and see. It usually takes under an hour on an account this size.
2. Rightsize compute before you consider committing to anything
AWS Compute Optimizer is free and reads your CloudWatch metrics to flag under-provisioned and idle resources, including "unattached EBS volumes, idle EC2 instances, and more." Turn it on before you touch instance types by hand. Two changes worth checking specifically:
- Instance size. A service provisioned for a launch-day traffic spike that never came back down to a smaller size is the single most common waste at this stage.
- Instance family. AWS's own page states Graviton-based instances "cost up to 20% less than comparable x86-based Amazon EC2 instances" for the same workload, for workloads that are already ARM-compatible. That is a ceiling, not a guarantee, and it depends entirely on your stack's compatibility, so test before you commit a production service to it.
3. Pick the right storage class, and set the lifecycle rule on day one
S3 storage classes carry minimum billable storage durations that matter more at small scale than the headline per-GB price: S3 Standard-IA and One Zone-IA carry a 30-day minimum, and both Glacier Flexible Retrieval and Glacier Instant Retrieval carry a 90-day minimum, while Glacier Deep Archive carries a 180-day minimum. Move an object that gets deleted or re-accessed before that minimum and you pay the early-deletion charge on top of what you were trying to save. The fix is a lifecycle rule set when you create the bucket, not a cleanup project six months later: build artifacts and logs older than 30 days move to Standard-IA, anything older than 90 days that is genuinely cold moves to Glacier. S3 Intelligent-Tiering is the safer default when access patterns are unpredictable, since AWS states there are "no retrieval charges, and no additional tiering charges apply when objects are moved between access tiers."
4. NAT Gateway and egress: the trap most seed teams do not see coming
A NAT Gateway bills two ways: an hourly charge, and a per-GB data processing charge on every byte that passes through it, in both directions. A single service pulling dependencies, calling third-party APIs, or shipping logs externally through a NAT Gateway can quietly become one of the largest line items on a small bill, because the processing fee applies whether the traffic is 1 GB or 10 TB. The fix that costs nothing to implement: route traffic to S3 and DynamoDB through VPC Gateway Endpoints instead of the NAT Gateway. That traffic never touches the NAT path at all, so the processing fee disappears for exactly the two services most backends talk to constantly. For everything else your service talks to over the public internet, the shape of the problem is the same one we cover in full, across all three major clouds, in the egress cost breakdown; this section is the seed-stage-specific corner of that same problem, the NAT Gateway tax that hits before egress volume itself gets large enough to notice.
5. Committed-use math: when it helps, and why it is premature for most seed teams
AWS Savings Plans offer savings of "up to 72%" against on-demand pricing in exchange for a one- or three-year commitment to a dollar amount of usage per hour. That number is real, and it is also the reason committed-use is the last lever on this list, not the first. A one-year minimum commitment assumes your architecture, instance families, and regions look roughly the same for the next twelve months. Most seed-stage teams change at least one of those within two quarters: a pivot in the data layer, a move off a monolith, a region change when the first enterprise customer requires data residency. Commit before that happens and you are paying for capacity you no longer run.
The AWS Enterprise Discount Program, the deeper discount tier some larger companies negotiate directly with AWS, is not relevant at this stage at all. AWS does not publish a fixed entry threshold, but third-party guides that track EDP negotiations put the practical floor around $500,000 to $1,000,000 in committed annual spend. A sub-Rs 5L monthly bill is roughly Rs 60 lakh a year, well under a tenth of that floor. Skip it, and skip any vendor pitch built around it, until the bill has grown by an order of magnitude.
Where an open-source investigator fits into this
Once the checklist above is done once, the harder problem is catching the next spike before it becomes a Slack thread at midnight. We built and open-sourced Ghost-hunter for exactly that: an AI investigator that reasons through a cost spike the way a senior SRE would, forming a hypothesis, running a read-only command to check it, and ruling options in or out, instead of a dashboard that shows you the shape of the spike and stops there. It is free, it runs locally against your own account, and it is one input into an audit, not a replacement for the judgment of the person reading its output. Details on the AI FinOps service page.
A same-week checklist
- Apply for whichever AWS Activate tier you qualify for, if you have not already, before you touch anything else
- Add your PAN to the AWS billing console so GST shows correctly on tax invoices
- Run
aws ec2 describe-volumes --filters Name=status,Values=available and delete or snapshot-and-delete what comes back
- Turn on AWS Compute Optimizer and act on anything flagged idle for more than two weeks
- Add a lifecycle rule to every S3 bucket that holds logs or build artifacts
- Check whether your NAT Gateway is carrying S3 or DynamoDB traffic that a VPC Endpoint could take off it for free
- Leave Savings Plans and EDP alone until your architecture has been stable for two straight quarters
When this becomes a job, not a checklist
The checklist above is a few hours of work, once. The part that actually compounds is what happens after: a new engineer spins up an oversized instance next quarter, a forgotten snapshot starts aging again, a new service gets built without a lifecycle rule. That is the ongoing cost review most companies say they will get to and never do, because nobody owns it as a job. It is also one of the three things a retainer with MatrixGard covers as standard, alongside the security posture and the deployment reliability nobody else owns either, at a fraction of the cost of hiring a senior cloud engineer, a DevOps engineer, and a security engineer separately. If the cost side alone sounds like a fit, the pricing page has the actual numbers, and a free 20-minute review will tell you which of the levers above already apply to your account.
Frequently asked questions
Does AWS bill Indian companies in INR or USD?
If your account's contact and billing address is in India, your agreement is with Amazon Web Services India Private Limited, and the invoice total is listed in INR, with GST added and a tax invoice you can claim as input tax credit if your PAN is on file.
What are AWS Activate credits, and does a seed-stage Indian startup qualify?
AWS Activate offers a self-funded "Founders" tier of up to $5,000 with no accelerator or investor required, and a "Portfolio" tier of up to $200,000 for startups backed by a participating accelerator, VC firm, or startup platform. Apply for whichever tier fits before spending engineering time on other optimizations, since credits reduce the bill immediately with zero engineering effort.
Should a seed-stage startup buy AWS Savings Plans?
Usually not yet. Savings Plans lock in a one- or three-year commitment to a specific level of usage in exchange for savings of up to 72% against on-demand pricing. That math only works once your architecture and instance mix have been stable for a couple of quarters. Committing earlier means paying for capacity you may not run once the architecture changes.
What is the single highest-leverage first step to cut an AWS bill under Rs 5 lakh a month?
Finding graveyard resources: unattached EBS volumes, unused Elastic IPs, stale snapshots, and forgotten load balancers. None of it is doing useful work, so removing it carries zero risk, unlike rightsizing a live service or changing a storage class.
Is Ghost-hunter free to use?
Yes. Ghost-hunter is an open-source AI cost investigator we built and released publicly. It runs against your own account and is one input into a review, not a substitute for someone deciding what the findings actually mean for your architecture.
When does cloud cost control stop being a one-time checklist and become a job someone needs to own?
Once the account has more than a couple of engineers who can provision resources independently, waste creeps back in between reviews. At that point the fix is a named owner doing this monthly rather than a founder remembering to do it once a quarter, which is the shape of an ongoing retainer rather than a one-off audit.
Methodology and sources
Every AWS figure in this post is quoted from AWS's own current documentation and pricing pages, fetched on 6 September 2026: AWS India account management, AWS Activate credits, AWS Compute Optimizer, AWS Graviton, Amazon S3 pricing, Amazon VPC pricing, and AWS Savings Plans. The AWS Enterprise Discount Program entry threshold is not published by AWS; the estimate cited is from a third-party FinOps guide and is labelled as such, not as an AWS-stated figure. No dollar or rupee saving in this post is invented; where a specific number is not verifiable for your account, we said so rather than guess.
About the author
Avinash S is the founder of MatrixGard, a fractional DevSecOps practice that acts as the cloud, infrastructure, and security team for early-stage startups, funded or bootstrapped, wherever they are. He runs the same kind of cost and security review this post describes as the opening move on every engagement, and publishes the honest version of what actually moves a small cloud bill rather than a generic checklist.
