How One Indian Startup Cut AWS Costs by 30% Using Trusted Advisor
May 05, 2026
Cloud costs can silently erode a startups runway, often without founders realising how much is being wasted. For early-stage companies running on AWS, every rupee saved on infrastructure can extend the timeline to the next funding round or product milestone. One Indian startup recently reduced its AWS bill by 30 percent using AWS Trusted Advisor, a tool that many founders overlook despite its potential for immediate cost savings. The key was not just identifying inefficiencies but acting on them with disciplinesomething that requires both technical awareness and operational rigour.
The Hidden Cost of Unoptimised Cloud Infrastructure
Startups often move fast to build and scale, prioritising speed over cost efficiency. This is understandableno founder wants to slow down development to tweak infrastructure. But over time, this approach leads to bloated cloud bills. Unused instances, over-provisioned resources, idle load balancers, and unoptimised storage add up. AWS Trusted Advisor, a built-in service available to all AWS customers, flags these inefficiencies in real time. The problem is not the lack of visibility but the lack of action. Many startups check the recommendations once and then ignore them, assuming optimisation is too complex or time-consuming.
The reality is that most cost-saving opportunities identified by Trusted Advisor are low-risk and high-impact. They do not require architectural overhauls or downtime. What they do require is a systematic approach to reviewing, prioritising, and implementing changes. The startup in question took this approach, treating cost optimisation as an ongoing engineering practice rather than a one-time audit.
How Trusted Advisor Works and Why It Matters
AWS Trusted Advisor is a service that analyses your AWS environment against best practices across five categories: cost optimisation, performance, security, fault tolerance, and service limits. For startups, the cost optimisation checks are the most immediately valuable. These include recommendations for idle resources, underutilised instances, reserved instance opportunities, and storage optimisations. The tool provides a clear list of issues, their potential savings, and step-by-step guidance on how to fix them.
What makes Trusted Advisor different from third-party cost tools is its integration with AWS. It has direct access to your usage data and can provide precise, actionable insights without requiring additional setup. For founders who are already stretched thin, this is a significant advantage. There is no need to install agents, configure dashboards, or learn a new interface. The recommendations are available in the AWS console, and many can be resolved with a few clicks.
The startup in this case had been using AWS for over two years without ever reviewing Trusted Advisor. When they finally did, they found over 20 active recommendations, each with potential savings ranging from a few hundred to several thousand rupees per month. The total estimated savings were close to 35 percent of their monthly bill. This was not an outliermost startups running on AWS for more than a year have similar inefficiencies.
The Step-by-Step Process to 30 Percent Savings
The startup did not achieve these savings overnight. They followed a structured process, treating cost optimisation as a project with clear milestones. Here is how they did it.
First, they exported the Trusted Advisor recommendations into a spreadsheet and categorised them by type: compute, storage, networking, and idle resources. This helped them prioritise the highest-impact changes first. For example, they found several EC2 instances that were running at less than 10 percent CPU utilisation for over a month. These were prime candidates for right-sizing or termination.
Next, they reviewed each recommendation with their engineering team to assess the risk. Some changes, like terminating unused Elastic IPs or deleting old snapshots, were low-risk and could be done immediately. Others, like downsizing production databases, required more planning to avoid performance issues. The key was to balance savings with stability. They did not implement every recommendation blindlythey tested changes in staging first and monitored the impact.
One of the biggest wins came from optimising their storage. They had been using gp2 EBS volumes for all their instances, including those that did not require high IOPS. Trusted Advisor flagged these as candidates for gp3 volumes, which are cheaper and offer better performance for most workloads. By migrating their non-critical instances to gp3, they reduced their storage costs by 20 percent without any downtime.
Another significant saving came from reserved instances. The startup had been running several on-demand instances for over a year. Trusted Advisor identified these as candidates for reserved instance purchases, which can reduce costs by up to 75 percent for long-term workloads. They purchased reserved instances for their production databases and core services, locking in lower rates for the next one to three years.
They also found several idle resources that had been forgotten. These included unused load balancers, old EBS volumes, and unattached Elastic IPs. Terminating these alone saved them over 5 percent of their monthly bill. The lesson here is simple: startups accumulate technical debt in their cloud infrastructure just as they do in their code. Regular cleanups are essential to prevent waste.
The Role of Engineering Discipline in Cost Optimisation
The startups success was not just about using Trusted Advisorit was about embedding cost awareness into their engineering culture. They started treating cloud costs as a first-class metric, alongside performance and reliability. This meant reviewing Trusted Advisor recommendations weekly, setting up cost anomaly alerts, and including cost optimisation in their sprint planning.
They also implemented a tagging strategy to track costs by team, project, and environment. This helped them identify which parts of their infrastructure were driving the most spend and where optimisations would have the biggest impact. For example, they found that their staging environment was costing nearly as much as production, despite being used only a few hours a day. By automating the shutdown of staging instances outside working hours, they reduced their staging costs by 60 percent.
Another important practice was setting up budgets and alerts in AWS Cost Explorer. This gave them early warnings when costs exceeded expectations, allowing them to investigate and take corrective action before the bill arrived. Many startups only realise they have a cost problem when they receive their monthly invoice. By then, it is too late to avoid the expense. Proactive monitoring is the difference between reactive firefighting and sustainable cost management.
Why Most Startups Fail at Cost Optimisation
Despite the availability of tools like Trusted Advisor, most startups do not achieve meaningful cost savings. There are three common reasons for this.
First, they lack ownership. Cost optimisation is often seen as the responsibility of the finance team, not the engineering team. But finance teams do not have the technical context to implement changes. Engineering teams, on the other hand, often view cost optimisation as a distraction from their core work. The startup in this case solved this by assigning a dedicated engineer to own cost optimisation, reporting directly to the CTO. This ensured that the work was prioritised and executed with technical rigour.
Second, they treat cost optimisation as a one-time activity. Cloud infrastructure is dynamicnew resources are spun up, workloads change, and usage patterns evolve. A one-time audit will not capture these changes. The startup made cost optimisation an ongoing practice, reviewing Trusted Advisor recommendations weekly and incorporating cost checks into their deployment pipelines.
Third, they fear breaking production. This is a valid concern, but it is often overstated. Many cost-saving changes, like terminating idle resources or switching storage types, carry minimal risk. Others, like right-sizing instances, require testing but are not inherently dangerous. The key is to approach optimisation with the same discipline as any other engineering change: test in staging, monitor in production, and roll back if needed.
The Long-Term Impact of Cost Optimisation
The 30 percent reduction in AWS costs was not just a one-time saving. It had a compounding effect on the startups runway and scalability. The money saved was reinvested into hiring, product development, and customer acquisition. More importantly, the discipline they developed around cost optimisation set them up for sustainable growth. They were no longer flying blindthey had visibility into their cloud spend and the tools to control it.
For other startups, the lesson is clear. Cloud cost optimisation is not about cutting corners or sacrificing performance. It is about eliminating waste, making informed trade-offs, and building infrastructure that scales efficiently. Tools like AWS Trusted Advisor make this possible, but they are only effective if used with intention. The difference between a startup that saves 30 percent on its cloud bill and one that does not is not technologyit is discipline.