The short answer
Work in order. Make spending visible and owned: tags activated for billing, budgets, anomaly alerts. Remove waste: idle instances, unattached volumes, old snapshots, non-production running all night. Rightsize with real utilisation data. Only then commit to Savings Plans or reserved capacity for usage that will continue; committing first locks in today's waste at a discount.
How AWS frames it
AWS's cost pillar of the Well-Architected Framework describes practising cloud financial management, being aware of spending and usage, choosing cost-effective resources, managing demand and supply, and optimising over time. The steps below turn that into a routine.
Step 1: Make spending visible and owned
Tag what costs money
Application, environment, owner, cost centre, so every bill line is explained. No sensitive data.
Activate tags for billing
Tags show in Cost Explorer only once activated, and can take up to 24 hours.
Cost Explorer monthly
13 months of history, forecasts, free console. Group by service, account, tag.
Budgets and anomaly alerts
Budgets warn on actual or forecast spend, not a cap. Anomaly detection uses machine learning.
Alerts to someone who acts
Email a named person with authority, or post to a chat channel.
An owner per account
Separate production, test and development accounts: clearer costs, easy non-production switch-off.
AWS guides: cost allocation tags, Cost Explorer, AWS Budgets, Cost Anomaly Detection.
Step 2: Remove waste
Waste is the fastest saving: removing it changes nothing that works. Look for:
- Low-use or unexplained instances and databases
- Unattached storage volumes
- Old snapshots and machine images
- Unused elastic IP addresses
- Idle load balancers
- Dev and test running evenings and weekends
- Logs kept forever by default
Scheduling non-production to stop outside working hours is often the easiest win in the account.
Step 3: Rightsize using real data
Servers moved from on-premises are often sized for a rare peak. AWS Compute Optimizer analyses utilisation (by default 14 days, after you opt in), recommends sizes for EC2, Auto Scaling groups, EBS, Lambda, RDS, Aurora and more, and flags idle resources. It is a starting point: check month-end or seasonal peaks, test smaller sizes outside production, change one thing at a time.
Storage too. S3 Lifecycle rules move ageing objects to cheaper classes and delete them when retention ends. But transitions carry per-request charges and some classes have minimum storage durations, so small or short-lived objects can cost more to move than they save.
Rather talk it through? We can review your AWS accounts, rank the savings by effort and risk, and set up the tagging and alerts that keep costs in check. Talk to a Promatics specialist
Step 4: Commit for steady usage
Once usage is clean and stable, Savings Plans lower prices for committing to a set compute spend per hour for one or three years (all, partial or no upfront). Compute Savings Plans span EC2 families, sizes and regions, plus Fargate and Lambda. Our advice: commit only to the baseline that will remain, not your peak; prefer shorter, flexible plans while your architecture changes; review coverage and utilisation quarterly.
Step 5: Look at architecture
Some costs fall only with design changes: managed services, newer or ARM-based (Graviton) instances where software supports them, caching, less data transfer between zones and to the internet. Plan them as engineering changes, with testing and risk.
Nigerian considerations
| Topic | What to do |
|---|---|
| Naira budgeting | AWS prices in US dollars, so the bill moves with the exchange rate. Budget in naira with the dollar figure alongside, and allow for movement. |
| Tax and payments | Confirm with finance how foreign-currency payments, VAT and withholding tax apply to AWS invoices. |
| Data protection | No major AWS region is in Nigeria, so workloads already run abroad. A cheaper region may conflict with NDPA transfer rules, sector requirements or customer contracts: check before moving storage, backups or workloads. |
| Latency | Choose the region balancing cost, performance for your users and compliance, not the cheapest alone. |
| Allocation | Reports grouped by tag make it easier to charge costs to departments, projects or funded programmes. |
What usually goes wrong
- Buying commitments first: a discount locked in on oversized, idle resources.
- Alerts nobody reads: budget emails to a shared mailbox or a former employee.
- One big clean-up, then drift: savings disappear within months without a monthly review.
- Deleting the wrong thing: a volume or snapshot that was the only backup.
A monthly AWS cost routine
- Review Cost Explorer by service, account and tag; note top five changes.
- Investigate every cost anomaly alert and record the cause.
- Check untagged spend and fix tagging at the source.
- Review idle and underused resources and Compute Optimizer findings.
- Confirm non-production schedules are working.
- Check Savings Plans coverage and utilisation (quarterly).
- Update the naira forecast at today's exchange rate; share with finance.
When to bring in help
With a handful of workloads and someone to run this routine monthly, AWS's own tools cover most of it. Bring in help when nobody can explain large parts of the bill, resources lack owners, rightsizing production feels risky or commitments involve significant sums. Our AWS deployment and cloud engineering team reviews your accounts, makes the changes safely and sets up the routine so savings last.
Sources and further reading
Product capabilities and guidance change. These are the primary sources this article relies on, checked on the review date above.
- Cost pillar, AWS Well-Architected Framework, Amazon Web Services documentation
- Tracking costs using AWS cost allocation tags, Amazon Web Services documentation
- Reviewing your costs and usage with AWS Cost Explorer, Amazon Web Services documentation
- Managing your costs with AWS Budgets, Amazon Web Services documentation
- Getting started with AWS Cost Anomaly Detection, Amazon Web Services documentation
- What is AWS Compute Optimizer?, Amazon Web Services documentation
- Managing the lifecycle of objects (Amazon S3), Amazon Web Services documentation
- What are Savings Plans?, Amazon Web Services documentation
This article is general information, not legal, accounting or security advice for your specific situation. Examples are hypothetical unless stated otherwise.