AWS Cost Reduction Through EC2 Rightsizing and Resource Cleanup
Business Challenge
An outdated eCommerce theme hurt usability and trust, while weak visuals, limited interactivity, and poor mobile experiences reduced conversions and repeat visits.
Technology Used
Blueprint
Bobcares updated the platform with a modern design, better navigation, and responsive interactions, improving engagement, conversions, and repeat visits.
The Client
As the platform expanded, AWS infrastructure grew across production, pre-production, and test environments. Eleven EC2 instances supported these environments. Over time, instance sizes increased while actual usage stayed low. Unused cloud resources accumulated quietly, pushing monthly AWS costs higher without adding value.
The Challenge
Oversized EC2 instances consumed unnecessary compute capacity, even though CPU and memory usage remained below ten percent. Unused S3 buckets, outdated EBS snapshots, stale AMIs, and excessive CloudWatch logs generated recurring charges without supporting active workloads. Orphaned network resources added to the clutter.
Limited visibility into usage and cost made it difficult to identify waste or connect spending with business needs. Opportunities for savings existed, but lacked clear data and a structured execution plan.
Why Bobcares
Bobcares was selected for experience in AWS cost governance, detailed infrastructure audits, and EC2 rightsizing aligned with real workload demand. The team focused on measurable savings, transparency, and client control over every decision.
What We Delivered
The work began with a detailed audit that mapped every resource to a business purpose. Usage data guided EC2 resizing decisions, while unused and outdated resources were carefully identified and approved for removal. Changes were implemented safely, supported by monitoring and validation.
The result was a cleaner AWS environment that matched actual platform needs and delivered sustained cost control.
Key Components and Implementation Highlights
Infrastructure Audit and Discovery
EC2 performance metrics, EBS usage, S3 storage, CloudWatch logs, and orphaned resources were reviewed across all environments. Each item was evaluated against current operational requirements.
EC2 Usage Analysis and Rightsizing
Multi-week CloudWatch data revealed consistent underutilization. Instance recommendations aligned capacity with real usage while preserving performance during peak activity.
Resource Cleanup and Cost Control
Unused S3 buckets, outdated snapshots, stale AMIs, excessive log groups, and unused networking components were removed after client approval, eliminating unnecessary monthly charges.
Safe Execution and Validation
Resizing took place during low-traffic periods. Backups were created before changes, followed by live monitoring to confirm stability and cost impact.
Key Aspects and Modules
- EC2 rightsizing across production, pre-production, and test environments.
- Cleanup of unused storage, snapshots, logs, and images.
- Cost visibility tied to actual resource usage.
- Controlled execution with rollback planning.
- Improved infrastructure hygiene and governance.
The Results
Key Metric |
Before |
After Implementation |
| EC2 Costs | High and growing | Significantly reduced |
| Storage Costs | Increasing | Stable and controlled |
| Instance Utilization | Below 10% | Balanced at 40–60% |
| Redundant Resources | Many present | Fully removed |
| Service Downtime | Possible risk | Zero downtime |
The Business Impact
The platform now operates on infrastructure aligned with actual demand, rather than assumptions.
Technologies Used
- AWS EC2
- Amazon S3
- Amazon EBS
- Amazon CloudWatch
