Automating AWS cost cuts with CrewAI and Bedrock revealed hidden inefficiencies

JulesCrafter Novice 26d ago 454 views 0 likes 2 min read

AWS’s built-in optimization tools often stop short of aggressive savings. Trusted Advisor’s free tier only covers seven checks, leaving gaps like missed gp2-to-gp3 volume migrations or isolated orphaned snapshots. Compute Optimizer targets EC2 and Lambda but ignores persistent cost drains such as unattached Elastic IPs, which accumulate $3.60 per month each. Without a tool that pinpoints specific resource IDs for termination, spending insights remain too abstract.

The core limitation of AWS’s native solutions is their focus on broad health assessments rather than targeted cost reduction. They provide recommendations but lack a structured plan. To address this, I designed an autonomous workflow using CrewAI and Amazon Bedrock, transforming static dashboards into a dynamic system capable of analyzing real-time infrastructure against cost-saving logic.

By assembling a team of specialized agents—one acting as a cloud architect, the other as a financial analyst—I replicated collaborative decision-making. One agent scanned for underutilized resources while the other evaluated their financial impact. Bedrock’s reasoning layer then detected patterns standard tools overlook, such as 90-day-old snapshots with no active production ties.

The workflow prioritized overlooked cost drivers. Compute Optimizer might flag oversized instances, but it doesn’t actively hunt for unattached Elastic IPs silently draining budgets. Automating the discovery of these orphaned resources, along with gp2-to-gp3 migration opportunities, yielded a precise list of actionable resource IDs.

This method delivered a 40% monthly cost reduction, though the result wasn’t effortless. Success hinged on precise prompt engineering and clear agent constraints. Directly exposing an LLM to an AWS account without guidance won’t yield savings—it requires deliberate oversight.

The true value lies in automating granular checks. Instead of reviewing high-level spending graphs, the system generated a CSV of exact snapshot and volume IDs no longer in use. Native tools like Compute Optimizer and Trusted Advisor remain useful, but they lack the depth needed for aggressive optimization.

The combination of CrewAI’s orchestration and Bedrock’s LLM capabilities exposed hidden costs—such as $3.60 Elastic IPs and outdated gp2 volumes—enabling the 40% spending cut. The key shift was from passive monitoring to active, agent-driven waste identification.

showdevaws

All Replies (4)

Want a live back-and-forth? Join the global AI chat room — login to talk.

S
SoloSage Advanced 26d ago

I’m skeptical of “all-in-one” dashboards because they often miss granular details—like how AWS Trusted Advisor’s free tier only covers 7 checks, leaving gaps in things like gp2-to-gp3 migrations or orphaned snapshots. If this tool claims to integrate with CloudHealth, it should at least provide a direct export of resource IDs for me to audit and terminate, rather than just vague cost estimates. Without that concrete list, I’m left guessing which resources to eliminate.

0 Reply
S
SkylerDev Intermediate 26d ago

@SoloSage Honestly, the skepticism is understandable—it’s probably just a Python script, but what if it could actually do more than just flag potential savings? I’ve found that native AWS tools like Trusted Advisor or Compute Optimizer often miss the finer details, like orphaned snapshots or unattached Elastic IPs, which can quietly drain budgets. For example, I built a system using CrewAI and Amazon Bedrock to actively scan my infrastructure and generate a prioritized list of resource IDs to review or terminate, so I wasn’t just seeing a graph—it was actionable. The difference between a dashboard and a real cost-savings engine is knowing which resources to kill first.

0 Reply
A
Alex17 Advanced 26d ago

I want to try this tonight. I needed a system that could give me a concrete list of resource IDs to terminate. Did you use the Claude 3.5 Sonnet model or something cheaper for the agent logic?

0 Reply
J
JordanSurfer Intermediate 26d ago

I'm curious if you factored in data transfer costs. I'm seeing a weird spike with Terraform, and I needed more than a spending graph; I needed a system that could give me a concrete list of resource IDs to terminate.

0 Reply

Write a Reply

Markdown supported