See your AWS spend and schedule the idle hours.
Explore AWS spending by service, environment, account or region. Set saving schedules for supported non-production resources when they do not need to run.
- Demo project
- Costs
Sample AWS cost explorer: $4,182.40 spent this month so far, lower than the same days last month, broken down by EC2, RDS, EKS, load balancing and S3. Beside it, a new saving schedule for the Development environment runs resources Monday to Friday from 08:00 to 18:00 and covers five resource types.
AWS cost management
What you get
A cost breakdown you can inspect and a defined schedule for selected resources, with operation status visible in Microtica.
What you bring
- A connected AWS account with the required permissions.
- To schedule resources, choose a supported environment or account resource group and AWS region.
How it works
Know what happens before you start.
- 01
Find the cost driver
Review the AWS cost breakdown. Filter by account, environment, region or service to see which part of the bill needs attention.
- 02
Choose the resources
Select a non-production target and supported resource types. Check exclusions and dependencies before stopping anything.
- 03
Set active hours
Configure active days and hours or use an on-demand schedule. Review operation status as resources stop and start.
AWS cost visibility
The current cost explorer groups spending by service, environment, account or region, with filters for each. It supports month-to-date and previous-month views.
Resource-aware schedules
Supported types include EC2, ECS/Fargate, EKS managed node groups, provisioned RDS and provisioned Aurora. Standalone Auto Scaling groups are an optional type. Aurora Serverless clusters are excluded.
“Microtica provided us with excellent guidance and support throughout the migration process, and the cloud platform has been a breeze to use since then. We are very thankful for the cost savings measures the platform provides.”
Access and control
Saving schedules change running capacity
These actions can stop instances or scale services and node groups down. Test on non-production workloads and check dependencies first. Savings vary with usage, resource types and cloud charges; no fixed percentage is promised.
Try it on one service.
Start free with a development project, or bring your setup to a demo.