How to Schedule RDS Instances: Pay for 50 Hours a Week, Not 168

Your production database has to run around the clock. Your dev, staging, QA, and demo databases don’t — but many AWS accounts run them 24/7 anyway.

To schedule RDS instances, you stop and start them automatically on a fixed weekly pattern, so non-production databases bill for compute only during working hours. A weekday 8am–6pm schedule uses about 50 of the week’s 168 hours — roughly 217 billed compute hours a month instead of 730. Storage and backups bill either way.

That’s the whole idea. The rest of this guide covers what actually happens when you stop an RDS instance, the three ways to automate it, the AWS behavior that breaks most homegrown solutions, and a checklist to run before you roll it out.

How much does RDS scheduling really save?

Run the numbers on a single database and the case makes itself.

Weekly heatmap: a weekday 8am–6pm schedule uses 50 of a week's 168 hours
A weekday 8am–6pm schedule uses 50 of a week’s 168 hours. The other 118 are compute you stop paying for.

One staging database on a business-hours schedule stops billing for 118 compute hours every week — about 6,100 hours a year. Few teams have just one non-production database. Multiply those idle hours across every dev, QA and demo instance and you get a large, predictable line on the bill you can remove with no re-architecting, no performance risk to production, and no multi-year commitment.

It’s the same logic behind scheduling your EC2 instances, applied to your databases.

RDS compute cost for three instance sizes running 24/7 versus on a business-hours schedule
The same three instance sizes, before and after a business-hours schedule.

What happens when you stop an RDS instance?

Stopping is not deleting. Your data, automated backups, endpoint, parameter groups, and option groups all survive. When the instance starts again it keeps the same endpoint, so connection strings don’t change and nothing downstream needs reconfiguring.

What you stop paying for: instance hours — the compute.

What you keep paying for:

  • Provisioned storage (gp3, io1/io2)
  • Automated backup and manual snapshot storage
  • Provisioned IOPS, where configured

On many non-production databases, instance hours outweigh storage, so stopping them removes the larger share of the spend even though storage keeps ticking.

Timeline of a stopped RDS instance automatically restarting after seven days
A stopped RDS instance starts itself again after seven days — and resumes billing for compute hours.

The 7-day auto-restart that breaks manual approaches

Here’s the AWS behavior that catches many teams: a stopped RDS instance automatically restarts after seven days.

Stop a staging database on Friday afternoon, forget it over a quiet sprint, and AWS brings it back online the following Friday — billing every hour after that, whether anyone connects or not. AWS does this so instances receive required maintenance and patching, and there’s no setting to disable it.

The practical consequence: “we’ll just stop them manually when we’re done” is not a cost strategy. It works for a week, then quietly reverses itself. Any real RDS scheduling approach has to re-stop instances after the auto-restart, which is exactly where the three methods below start to differ.

When the 7-day rule actually bites: a daily business-hours schedule never leaves a database stopped for a full week. It stops every evening and starts every morning, so the auto-restart rarely comes into play. The rule matters when a database is parked for longer: over the holidays, between projects, or when the plan is “keep it off until someone needs it”. AWS brings those databases back during their maintenance window to apply maintenance, then leaves them running.

Which RDS instances can’t be stopped

Confirm your fleet before you automate:

  • Instances with read replicas, and read replicas themselves
  • SQL Server in a Multi-AZ deployment
  • Clusters and instances that are part of a Blue/Green deployment

For Aurora, you stop the whole cluster rather than individual instances — and the same 7-day auto-restart applies. If the workload suits it, Aurora Serverless v2 can scale down to zero ACUs when idle on supported engine versions (with minimum capacity set to 0), reaching a similar outcome without explicit scheduling — storage still bills. For provisioned Aurora and standard RDS, scheduling is the lever.

Method 1: Stop RDS instances manually

The console path takes about thirty seconds: RDS → Databases → select the instance → Actions → Stop temporarily.

Why it fails at scale: it depends on a human remembering, every evening and every Friday, across every environment — and on that same human noticing when the 7-day auto-restart undoes the work. In practice, manual stopping rarely survives more than a few weeks.

Method 2: Automate RDS scheduling with Lambda and EventBridge

The standard DIY pattern: an EventBridge rule fires on a cron schedule, invokes a Lambda function, and the function stops or starts every RDS instance carrying a specific tag such as Schedule=business-hours.

To make this production-ready you’ll also need:

  • A mirrored start function
  • Two schedules — classic EventBridge rules run cron in UTC, so daylight saving shifts your “8am” twice a year; use EventBridge Scheduler instead, which accepts a time zone and adjusts for daylight saving
  • An IAM role with rds:DescribeDBInstances, rds:ListTagsForResource, rds:StopDBInstance, rds:StartDBInstance
  • Error handling for instances that are mid-backup, mid-modification, or otherwise not in a stoppable state
  • Separate logic for Aurora clusters, which use different API calls
  • A recurring job to re-stop instances that AWS auto-restarted on day seven

Best for: teams with one or two environments, spare platform-engineering capacity, and a tolerance for owning internal tooling.

The honest total cost of ownership: the code is now a small internal product. Schedules live in cron expressions, so “staging should stay up until 8pm on Thursdays now” becomes a pull request rather than a settings change. There’s no dashboard showing what’s scheduled, what got skipped, or how much was actually saved — and the day you want the same behavior for EC2, Auto Scaling Groups, or a managed database outside AWS, you’re extending it again.

What about AWS Instance Scheduler? AWS publishes a CloudFormation solution that packages this pattern more robustly than a hand-rolled Lambda. It’s a legitimate option — but you’re still deploying and maintaining stack infrastructure, schedules live in DynamoDB and are managed with a command-line tool (or by editing the table), so there’s no graphical interface a non-engineer can use. It’s a solution you operate, not a service you use.

On the 7-day restart, Instance Scheduler does better than DIY. By default it adds each database’s preferred maintenance window to its schedule as a running period. It starts the instance for the window and stops it again once maintenance is complete. If maintenance overruns the window, the instance keeps running until the first scheduling interval after it finishes. If a database comes back up outside its schedule for any other reason, AWS’s documentation says it is stopped before the next scheduled stop only when the schedule’s enforced option is turned on.

Skip the maintenance
CloudAvocado schedules RDS, Aurora, EC2, and Auto Scaling Groups from one visual calendar — no Lambda functions, no CloudFormation stacks, no cron. Start a free trial →

Method 3: Schedule RDS instances without scripts, using CloudAvocado

This is the gap CloudAvocado was built to close: scheduling that takes minutes to set up and nothing to maintain afterwards.

Connect your AWS accounts through a standard IAM role, and CloudAvocado automatically discovers your RDS instances and Aurora clusters alongside your EC2 instances and Auto Scaling Groups. Then:

  1. Select a resource — or a whole tag group. Schedule every database tagged env:staging in a single action rather than one at a time.
  2. Draw the schedule on a weekly calendar. Weekdays 8am–6pm in your team’s local timezone. No cron syntax, no UTC arithmetic, no daylight-saving bugs.
  3. Leave it alone. CloudAvocado stops and starts on schedule. If AWS restarts a stopped database on day seven, CloudAvocado stops it again right away, with no extra setting to turn on, so instances don’t quietly come back online and start billing.

Three things that matter once it’s running:

  • Overrides without tickets. An engineer who needs staging at 9pm clicks start, works, and the schedule resumes on its own. Nobody edits automation code to work late.
  • Savings you can actually report. Every scheduled resource shows what it would have cost running 24/7 versus what it actually cost — the number finance asks for, without building a report.
  • One system across your whole non-production stack. The same schedules cover EC2, RDS, Aurora, and Auto Scaling Groups, so application servers and their databases sleep and wake together instead of drifting out of sync.

Savings start the first night a schedule runs, so they show up in the current month’s bill rather than the next quarter’s forecast.

Which RDS scheduling method should you use?

ManualLambda + EventBridgeAWS Instance SchedulerCloudAvocado
Typical setup timeSeconds per instance1–3 daysHalf a day to 2 days~5 minutes
Ongoing maintenanceEvery evening, foreverYou own the codeYou own the stackNone on your side
Handles the 7-day auto-restartNoOnly if you build itYes, by default: runs through the maintenance window, then stopsYes, stops it again right away, no setting needed
Timezone / DST handlingHuman judgmentUTC with rules; time zones with EventBridge SchedulerConfigurableBuilt in
Schedule changesN/ACode changeCLI or DynamoDB editClick and drag
Aurora clustersManual, separate actionSeparate API calls to writeSupportedSupported
Override for late workManual startManual startManual startSelf-service, schedule resumes
Savings reportingNoneBuild it yourselfCLI estimate only, no per-resource reportPer-resource, automatic
Covers EC2 and ASGs tooManualExtend the codeSupportedSupported
Best forOne database, one-offTeams with platform capacity to spareTeams standardized on AWS-native toolingTeams who want scheduling to just work

In short: if you have platform-engineering capacity to spare and only two environments, the Lambda route is perfectly reasonable. What doesn’t hold up is the manual route — it depends on a human remembering, and the 7-day auto-restart silently undoes it.

Before you roll it out: a 5-point checklist

  1. Storage still bills. Stopped isn’t free. If a database has been stopped for months, the real decision is snapshot-and-delete, not schedule.
  2. Check what’s stoppable. Read replicas and their sources, SQL Server Multi-AZ deployments, and Blue/Green deployments are excluded.
  3. Mind your pipelines. CI jobs, nightly ETL, and scheduled tests that touch staging must run inside the “on” window — or the window must stretch to cover them.
  4. Expect pending changes at start. Pending parameter- or option-group changes apply when the instance starts, and skipped maintenance catches up in the next maintenance window.
  5. Start with one environment. Put staging on a business-hours schedule, then compare two weeks of billing. That delta will make the case for the rest of your estate more convincingly than any projection.

Frequently asked questions

How much can I save by scheduling RDS instances? A weekday 8am–6pm schedule bills about 50 of a week’s 168 hours — roughly 217 of a month’s 730. You stop paying for the other ~118 compute hours each week. Storage and backups continue to bill, so the total saving on a given database depends on how much of its cost is storage rather than instance hours.

Does stopping an RDS instance delete my data? No. Data, automated backups, parameter groups, and the endpoint are all preserved. The instance restarts with the same endpoint, so connection strings don’t change.

Why does my stopped RDS instance keep restarting? AWS automatically starts any RDS instance that has been stopped for seven days so it can receive required maintenance. The behavior can’t be disabled — scheduling automation has to detect and re-stop those instances. CloudAvocado stops it again as soon as it comes back up, with nothing to configure.

Can I schedule Aurora clusters? Yes, but you stop and start the cluster rather than individual instances, and the 7-day auto-restart still applies. Aurora Serverless v2 is an alternative, since it can scale to zero ACUs when idle.

Is AWS Instance Scheduler free? The solution is open source with no license fee, but you pay for what it deploys — Lambda, DynamoDB, KMS, CloudWatch Logs and Metrics. AWS estimates roughly $9 to $630 a month depending on fleet size, plus the engineering time to deploy, configure, and maintain the stack.

What else should I schedule besides RDS? Application servers should sleep on the same pattern as their databases. Start with EC2 instance scheduling, then extend to Auto Scaling Groups so entire non-production environments power down as a unit.

Start with one database

Non-production databases running 24/7 are among the most predictable waste on an AWS bill — and the easiest to remove, because nothing about the architecture has to change. Pick your staging database, put it on a business-hours schedule this week, and check the numbers in two weeks.

If you’d rather not maintain Lambda functions and cron expressions to get there, start your free CloudAvocado trial — connecting an AWS account and scheduling your first RDS instance takes about five minutes, and the savings start the same night.

AWS Instance Scheduler vs CloudAvocado: When Native Is Enough and When It Isn’t

AWS has no managed scheduler for non-production resources. What it offers is Instance Scheduler, a CloudFormation stack you deploy and maintain, and a Quick Setup wizard that covers EC2 and nothing else. Both are fine for a small, single-account estate of EC2 and RDS.

They stop at containers, SageMaker, overrides, a UI, and anything that needs ordering. Every limit in this post links to AWS’s own documentation or an open issue on AWS’s own GitHub repository.

CloudAvocado covers EC2, RDS, Auto Scaling, ECS, EKS, DocumentDB, SageMaker and MongoDB Atlas on one schedule, with snooze, an audit log and dashboards across accounts, and nothing to deploy. This post lays out where the native tools are enough and where they are not.

What AWS gives you natively

AWS has no managed scheduling service. It has a solution you deploy, a Quick Setup wizard, and the building blocks to write your own. Ask on re:Post how to shut an EC2 instance down every night and the accepted answer lists exactly those three routes.

OptionServicesHow you configure itCostMaintained by
Instance Scheduler on AWSEC2, Auto Scaling groups, RDS, Aurora, DocumentDB, Neptune (supported services)CloudFormation hub and spoke stacks, then a Python scheduler CLI writing to a DynamoDB table (CLI docs)AWS estimates $9.15 to $630 per month for the Lambda, DynamoDB, CloudWatch and KMS it runs on (cost page)You. It is an open-source solution you deploy and upgrade
SSM Quick Setup Resource SchedulerEC2 only (docs)Console wizard: one tag key and value, days of the week, start and stop timesNo charge for Quick Setup itselfAWS runs it; you own the tags
EventBridge + Lambda (DIY)Anything with an APICron rules, a function per service, IAM roles per accountCents in Lambda, plus engineering hoursYou
Per-service scheduled scalingECS services, EKS node groupsScaling actions you wire yourself; for EKS, AWS’s own cost guide points to sample Kubernetes CronJobs (Prescriptive Guidance)No charge, except the timeYou, one mechanism per service

None of this is bad. Instance Scheduler is solid engineering and AWS keeps it patched. The question is what it does not do, because that list is where your hours go.

Where it stops

Every item below is either in the AWS documentation or an open issue on the Instance Scheduler GitHub repository as of this writing.

  • Containers. ECS and EKS are not on the supported list. ECS Fargate scheduling was requested in November 2024 (#582) and again in August 2026 (#702); the reply was “We’ve added it to our backlog.” For EKS, AWS’s cost guide tells you to scale dev and staging to zero with sample CronJobs. That is advice, not a scheduler.
  • SageMaker. Not supported. A request for SageMaker endpoint support, #601, has been open since March 2025.
  • No override or snooze. Three open requests ask for a way to say “leave this one alone until Thursday”: an instance override (#598), an exclusion tag (#641, “added to our backlog for evaluation”) and an official ignore option (#685). Quick Setup is event-driven: it starts whatever is stopped at the start time, so an instance someone stopped on purpose comes back in the morning and nobody knows who stopped it or why.
  • No UI. The scheduler CLI page is the configuration surface: create, update and delete periods and schedules from a terminal. One caveat there is worth reading twice: update-schedule and update-period remove any argument you omit. Expanded dashboards are an open request (#651).
  • No ordering. Periods are defined by begin time, end time, weekdays and months (CLI docs). There is no flag for “start the database, then the app servers.” You stagger times by hand. Also, only one one-sided start per day is supported, so an every-four-hours schedule silently did nothing (#542).
  • Quick Setup is one tag. Each configuration targets a single tag key and value, EC2 only, up to 5,000 instances per configuration per Region (docs). Two teams with two timetables means two configurations.
  • RDS restarts itself after seven days. You can stop a DB instance for up to seven days, then RDS starts it for maintenance. The re:Post workaround is to schedule a one-hour start every week so AWS never does it for you. A scheduler that does not know this leaves you paying for a database nobody started.
  • Restarts can fail on capacity. In January 2026 AWS added an opt-in retry on alternate instance types. That AWS shipped it tells you how often a morning start used to fail on capacity.
  • Detection is not action. Compute Optimizer flags idle resources across twelve types, but the recommended actions are manual. The AWS FinOps Agent, in preview since June 2026, runs on a role for reading cost, usage and operational data; it opens tickets, it does not stop instances. Something still has to turn the thing off.

What “free” costs

Instance Scheduler has no license fee. It does have a bill. AWS’s own cost page estimates about $9.15 a month for a small deployment (5 accounts, 20 resources, 3 schedules), about $161 for a medium one (250 accounts, 1,000 resources, 15 schedules) and about $630 for a large one (1,000 accounts, 5,000 resources, 500 schedules). The components are Lambda, DynamoDB, CloudWatch Logs, CloudWatch Metrics and KMS, running every five minutes.

Then there is upkeep. Between April and October 2026 the project shipped a dozen releases, v3.2.2 through v3.2.13, all dependency, security and bug fixes (changelog). Each is a stack update someone schedules, runs and checks. Add onboarding a new account, debugging a schedule that did not fire, and answering “why is staging up on a Sunday” in Slack.

The clearest sign of what the hours are worth: consulting firms sell Instance Scheduler setup as a professional service on AWS Marketplace, with pricing by private offer. When a free tool has a paid installation market, the tool was never the cost.

Why scheduling first

A week has 168 hours. A team that works roughly ten hours a day on weekdays uses about 50 of them. A non-production resource that nobody turns off is billed for all 168. Rightsizing changes the price per hour; scheduling changes the number of hours, and it is reversible the next morning.

One worked example with on-demand numbers you can swap for your own: 10 instances at $0.20 per hour, which is 10 x $0.20 = $2.00 per hour for the group.

Hours on per weekCost per weekCost per year (x52)
Always on168168 x $2.00 = $336$17,472
Business hours5050 x $2.00 = $100$5,200
Difference118$236$12,272

Ten small instances, one schedule, about $12,000 a year. A database, an EKS node group or a SageMaker notebook costs more per hour than $0.20, which is why the services a scheduler covers matter more than its price. The same arithmetic, with a larger fleet, is in the ParkMyCloud comparison.

AWS Instance Scheduler alternative: CloudAvocado vs native vs DIY

CloudAvocadoInstance Scheduler on AWSEventBridge + Lambda
StatusSaaS, 14-day free trial, listed on AWS MarketplaceOpen-source solution you deploy, v3.2.13 (October 2026)Your code
SetupOne IAM role created from a shown permissions list, no agents; free read-only scan firstCloudFormation hub stack, a spoke stack per account, scheduler CLIFunctions, roles and cron rules per account
EC2 and RDSYes; RDS from the Advanced planYes, plus Aurora, DocumentDB, NeptuneIf you write it
ECS and EKSYes: ECS services, EKS node groups to zero and back (Pro)No (#702 open)If you write it, per service
SageMaker, ASG, AtlasSageMaker notebooks, Auto Scaling groups, DocumentDB, MongoDB Atlas, plus Google Cloud and Azure (Pro)ASG and DocumentDB yes; SageMaker no (#601); AWS onlyAWS only, if you write it
Tag schedulesBy tag or individually; autotagging applies schedule tags to new resourcesBy tagBy tag, if you write it
SnoozeOn a schedule or a single resource; it rejoins the schedule afterwardsNot built in (#641, #685, #598)If you write it
Multi-account dashboardAcross accounts, tags and regionsNo console; dashboards requested in #651CloudWatch, if you build it
Savings reportingWeekly savings digest by email, dashboardsA CLI usage estimate per scheduleNone unless built
Audit logEvery actionCloudWatch LogsCloudWatch Logs
OrderingComing (Environments)NoIf you write it
Who can run itAnyone with a seat; SSO on ProWhoever has the CLI and AWS credentialsThe engineer who wrote it
CostFree for 10 resources; $49/month for 25; $299/month for 100; $3/month per extra resourceAbout $9.15 to $630/month in AWS charges, plus upkeep hoursCents in Lambda, plus engineering hours

Two rows deserve a note. Snooze is the one I hear about most: someone needs staging up late for a demo, or down for a week, and wants the schedule to pick back up on its own. In CloudAvocado that is one click on the resource or the schedule, and the audit log records it. Ordering is the one we have not shipped. Environments, which start and stop a group of resources in sequence, is in development, and I will not call it available until it is.

When to use the native tool

The native tools are the right choice when most of this is true:

  • One account, or a handful, all EC2 and RDS.
  • One schedule, or two, that rarely change.
  • The only people who need to change a schedule already have AWS credentials and a terminal.
  • Nobody needs to pause a resource for a day and have it rejoin the schedule automatically.
  • Policy says every tool must run inside your own account, so a SaaS with an IAM role is off the table.
  • The Quick Setup wizard covers your estate: EC2, one tag, one timetable.

If you ticked most of those, deploy Instance Scheduler or Quick Setup this week and move on. If you ticked two or fewer, the difference is time: with CloudAvocado there is no CloudFormation stack to deploy per account, no scheduler CLI to learn, no release to roll out every few weeks, and no Lambda to debug when a start fails. Connect an account, set working hours, pick resources by tag, and the first schedule runs that night. The hours your engineer would spend maintaining a scheduler go back to the work you hired them for.

Your first schedule in five minutes

  1. Connect an account. Create one IAM role from the permissions list CloudAvocado shows you. No agent. The first connection is read-only, so nothing is stopped until you say so.
  2. Read the scan. It lists your EC2, RDS, ECS, EKS, Auto Scaling groups, DocumentDB and SageMaker notebooks across accounts, tags and regions, with what is running 168 hours a week.
  3. Pick the resources and the hours. Select by tag, say Environment=dev, or tick resources one by one. Set weekday hours in your time zone, give staging a different timetable from dev if you like, and exclude anything you are unsure about. The EC2 scheduling walkthrough shows each screen.
  4. Switch on autotagging and the digest. New resources matching your tag get the schedule tag automatically, so next month’s dev box does not run all weekend. The weekly email tells you what was stopped and for how long. When someone needs an exception, they snooze it and the schedule resumes on its own.

FAQ

Is CloudAvocado an AWS Instance Scheduler replacement?

For EC2, Auto Scaling groups, RDS and DocumentDB, yes, with the same tag-based approach and no stack to maintain. It also covers ECS, EKS node groups, SageMaker notebooks, MongoDB Atlas, Google Cloud and Azure, which Instance Scheduler does not. It does not cover Neptune today.

Does it need an agent?

No. CloudAvocado connects through an IAM role you create from a permissions list we show you. The only optional agent is a small EC2 schedule agent for teams that want a pre-shutdown action to run on the instance. Scheduling itself never needs it.

Will it touch production?

Only resources you put on a schedule are ever stopped. The first scan is read-only, you choose resources by tag or by hand, any resource can be excluded, and every start and stop goes to the audit log. If a production instance carries a dev tag by mistake, the scan is where you see it before any schedule runs.

What about the RDS seven-day restart?

AWS starts a stopped RDS instance after seven days for maintenance (re:Post). A database on a weekday schedule is started every working morning, so it is never stopped seven days in a row and the restart never fires. If you snooze a database off for longer than a week, RDS will start it whatever tool you use; give anything you want down for weeks a one-hour weekly start. Storage bills while stopped either way; that is RDS, not the scheduler. For the full picture, see how to schedule RDS instances.

Can I keep Instance Scheduler for some accounts?

Yes. Connect only the accounts with ECS, EKS or many hands on them, and leave a working Instance Scheduler stack alone elsewhere. Just keep each resource on one scheduler, not two, so start and stop events do not fight.

Connect an account and run the free read-only scan. It takes five minutes and shows you what is running 168 hours a week before you schedule anything.

The ParkMyCloud alternative that schedules containers too

If you searched for ParkMyCloud and ended up here, you already know the story. Turbonomic bought it in 2019. IBM bought Turbonomic in 2021. The simple “park your instances at night” tool got absorbed into an enterprise platform, and the teams who used it for its simplicity were left choosing between something heavy and something hand-rolled.

CloudAvocado was built for exactly that gap. It turns non-production resources off outside working hours and back on before the team arrives. Setup takes about five minutes. And unlike ParkMyCloud, it doesn’t stop at EC2.

Why scheduling is still the first thing to do

The math is simple. A dev environment used weekdays 8 to 7 is idle 13 hours a night plus the whole weekend. That’s 118 of 168 hours each week – about 70% unused.

Savings Plans make those hours cheaper. Scheduling removes them. Nothing to re-architect, and ROI is shown right away.

A quick example

34 on-demand instances at $0.20/hour, scheduled to business hours only:

PatternHours / monthCost / monthSavings
24×7~730$4,960–
Weekdays only (24h)~521$3,54029%
Business hours (55h/week)~239$1,620~67%

Roughly $3,300 a month, or $40K a year, from one schedule. And that’s the EC2 line only. In most accounts I see, the RDS instances, ECS services and EKS node groups running next to those instances cost more than the instances do.

What ParkMyCloud got right, and what it missed

ParkMyCloud proved that a scheduler most people can operate beats a FinOps suite most people can’t. That part still holds.

What it missed is how non-prod environments are built now. A few things a replacement has to do:

Cover containers and databases. Stopping the EC2 nodes under an EKS node group saves nothing if the autoscaler brings them back. CloudAvocado scales ECS services and EKS node groups to zero outside the schedule and restores the desired count before work starts. RDS, Auto Scaling groups, SageMaker notebooks and MongoDB Atlas clusters get the same treatment. This is the biggest difference between CloudAvocado and the EC2-only tools still around, including ParkMyCloud itself.

See every account in one place. Most orgs run dozens of AWS accounts. You should see utilization and savings for all of them on one screen, without standing up a governance platform to get there.

Leave production alone by default. The reason teams hesitate to automate shutdowns is the fear of breaking something real. Only tagged or selected resources are scheduled. Everything else is untouched.

Install nothing. Access is a cross-account IAM role with least-privilege permissions. No agents, no stored keys.

CloudAvocado vs ParkMyCloud vs AWS Instance Scheduler vs DIY


ParkMyCloud (legacy)AWS Instance SchedulerLambda + EventBridge scriptsCloudAvocado
StatusAbsorbed into IBM TurbonomicActive, self-hosted CloudFormation solutionYou own itActive, self-serve SaaS
SetupMinutesCloudFormation stack + DynamoDB config + CLIHours to days, per account~5 minutes per account
EC2, RDSYesYesIf you write itYes
ECS / EKS scale-to-zeroNoNoIf you write itYes
SageMaker, ASGs, MongoDB AtlasNoLimitedIf you write itYes
Tag-based schedulesPartialYes, via tag syntaxIf you write itYes, with per-resource overrides
Multi-account dashboardYesNo UINoYes
Savings reportingYesNoNoYes
Who can run itAdminsWhoever maintains the stackWhoever wrote the scriptAnyone with dashboard access
CostPer resource, contractFree software + Lambda/DynamoDB + your timeFree software + your timeFree trial, then usage-based

The AWS Instance Scheduler is a great tool. If you have one account, only EC2 and RDS, and someone who enjoys maintaining CloudFormation, use it. Once you have containers, several accounts, or people outside the platform team who need to change a schedule, “free” stops being free.

Your first schedule in five minutes

  1. Connect an AWS account. Deploy the IAM role. CloudAvocado discovers EC2, RDS, ECS, EKS, SageMaker and Auto Scaling resources across regions.
  2. Set working hours. For example weekdays 08:00–19:00 in your team’s time zone.
  3. Attach it to a tag. env=dev, env=test, env=staging – or pick resources one by one.
  4. Review and apply. The dashboard shows what will stop, when, and the projected saving.

Most teams see the first savings in Cost Explorer the next day.

Moving from ParkMyCloud

The mapping is simple. ParkMyCloud teams become tags. Parking schedules become CloudAvocado schedules with the same windows. Auto-assignment policies are just how tags work here. The one new thing you’ll do is add the RDS, ECS and EKS resources ParkMyCloud couldn’t see.

Gotchas (and how CloudAvocado handles them)

  • Instances that need to shut down cleanly. Some workloads shouldn’t be killed mid-job. The EC2 schedule agent runs pre-shutdown actions before stopping an instance.
  • Someone needs the environment tonight. Pause the schedule for that resource. It rejoins the schedule automatically afterwards.
  • Untagged resources. Autotagging applies your schedule tags to new resources so coverage doesn’t drift.
  • Elastic IPs and stopped-instance storage. Stopping doesn’t zero the bill – EBS volumes and unattached EIPs still charge. Worth a separate clean-up, but small next to compute.

FAQ

  • Is CloudAvocado affiliated with ParkMyCloud or IBM? No. It’s an independent product built for the same job after ParkMyCloud was folded into Turbonomic.
  • Does it need an agent on my instances? No. A cross-account IAM role and native AWS APIs. The optional EC2 agent is only for pre-shutdown actions.
  • Can it stop EKS and ECS, not just EC2? Yes. ECS services and EKS node groups scale to zero outside the schedule and back before working hours.
  • Will it touch production? Only resources you tag or select are scheduled. Production stays out by default.
  • How long until I see savings? About five minutes to set up. Savings show on the next day’s bill. Typical non-prod savings are 30–60%, up to ~70% for strictly business-hours environments.
  • Need a simple AWS cost optimization solution?
  • ParkMyCloud showed that a light scheduler is worth to use to a teams with and without a heavy FinOps suite. CloudAvocado picks that up and extends it to the containers, databases that make up today’s non-prod bill.

Schedule MongoDB Atlas M20 Clusters: Pay for ~217 Hours a Month, Not 720

Quick answer: can you pause MongoDB Atlas clusters on a schedule? Yes, for dedicated M10+ clusters that don’t use NVMe storage. Flex and Free clusters can’t be paused. A paused cluster bills only for storage. Atlas resumes it automatically after 30 days, and it must run 60 minutes after resuming before it can be paused again. Atlas has no pause-on-schedule setting, so you either build one (a scheduled job or Atlas trigger that calls the Admin API) or use a scheduler like CloudAvocado, which also re-pauses clusters after the 30-day auto-resume.

Atlas has no equivalent of AWS Savings Plans or Reserved Instances; it offers its own subscription credits instead. That makes scheduling the main lever for non-production clusters. An M20 left on 24×7 bills about 720 hours a month; on a weekday business-hours schedule it needs about 217.

Why schedule Atlas now?

  • On‑demand compute adds up: An M20 is $0.20/hour (about $144/month for 720 hours, 24×7; region may vary). MongoDB
  • Atlas has its own commits: You can buy Atlas subscription credits (monthly/annual). That’s not the same as AWS Savings Plans/RIs. MongoDB
  • Most dev/test clusters run < 50 hours/week: Matching runtime to working hours eliminates the majority of compute spend.

What Atlas supports natively (and the limits)

Atlas Pause/Resume (UI, CLI, or Admin API) works for M10+ clusters that do not use NVMe, for up to 30 days, and you must let a cluster run 60 minutes after resuming before pausing again. While paused, Atlas charges only for storage(compute and data transfer stop). Flex and Serverless cannot be paused. MongoDB
Why teams still struggle with DIY: You end up wiring cron/Lambda, tracking 30‑day auto‑resume, honoring the 60‑minute run rule, rotating API keys, and remembering which projects/regions are eligible.

How CloudAvocado handles Atlas scheduling

    • Connect Atlas with a scoped API key.
    • Discover clusters across projects/regions (Atlas) alongside your AWS resources in one dashboard.
    • Pick a schedule (e.g., Weekdays 09:00–19:00)
    • Apply by tag or bulk‑select; new clusters inherit the schedule automatically.

Under the hood, CloudAvocado calls the Atlas Admin API for you, re‑pauses clusters after Atlas’ 30‑day auto‑resume.

The math for an M20 used < 50 hours/week

Pattern Hours / month Cost @ $0.20/hr Hours not billed vs 24×7
24×7 (baseline) 720 $144.00 —
Weekdays always‑on (24h × 5d) ~520 $104.00 ~200
Business hours (10h × 5d ≈ 50h/week) ~217 $43.40 ~503

Notes: Uses 50 h/week × ~4.33 weeks/month ≈ 216–217 h. Storage continues to bill while paused; compute and data transfer do not. MongoDB
Scale that across three M20 dev clusters and you’re saving ~$300/month on compute before any rightsizing.

Gotchas (and how CloudAvocado avoids them)

  • Eligibility: CloudAvocado flags clusters that can’t pause (Flex, Serverless, NVMe, some multi‑region setups). MongoDB
  • 30‑day auto‑resume: It re‑pauses if your schedule still applies. MongoDB
  • 60‑minute cool‑down: It waits the required hour after resume before pausing again. MongoDB
  • Warm‑up time: Search indexes/backups can trigger work after resume, consider that time. MongoDB
  • Commit vs. schedule: If you buy Atlas subscription credits, scheduling prevents you from burning them on idle hours but it won’t retroactively reduce a commitment. MongoDB

Next steps

  • Start a free CloudAvocado trial, connect your Atlas project and AWS accounts, and watch tomorrow’s dashboard reflect real savings.
  • Share this guide with your DBA + FinOps teams; standardize on < 50 hours/week for non‑prod as your default policy.

How to Schedule AWS EC2 Instances in 5 Minutes

Quick answer: how do you schedule EC2 instances to stop and start automatically? Tag the instances, then let a scheduler stop them outside working hours and start them before work. AWS has two free options: Systems Manager Quick Setup Resource Scheduler (EC2 only, set up in the console) and Instance Scheduler on AWS (a CloudFormation stack you deploy and run, which also covers RDS and Auto Scaling groups). A managed tool such as CloudAvocado does the same with nothing to deploy, and also covers RDS, Auto Scaling groups, ECS and EKS. See AWS Instance Scheduler vs CloudAvocado for a side-by-side.

Amazon EC2’s pricing means you’re billed for every second an instance is running – even if it’s sitting idle. Most development, testing environments don’t need 24/7 compute even though companies often leave these instances running constantly. This idle time translates to extra cloud spend. If your instances are only used ~10 hours a day on weekdays (50 hours/week), you’re billed for 168 hours a week but use about 50, so shutting them down after hours stops paying for the other 118. Usually dev teams isn’t working 24/7, but dev environments never stops. I want to share options how to schedule AWS EC2, RDS, ECS, EKS.

Why AWS Resource Scheduling Matters More Than Ever

As I mentioned above – most companies use their AWS instances run 24/7. The math is simple but painful: if your team works 40 hours per week, you’re paying for 128 hours of unused compute time.

Here’s what I typically see when auditing AWS accounts:

  • Development environments running 24/7 with no need
  • Test instances that haven’t been accessed in weeks but still running
  • Many test instances was used for a couple days and abandoned after that for weeks

The solution isn’t complex – it’s about aligning resource availability with actual need through scheduling.

Real Cost Impact: AWS Scheduling Examples

Lets look on sample dev environment with numbers:

Scheduling Strategy Instance Type Usage Pattern Monthly Cost Hours not billed per month
Always On (Baseline) 10 × m6i.xlarge 720 hrs/month $1,382.40 –
Weekend Shutdown 10 × m6i.xlarge Weekdays 24/7 $921.60 ~240 per instance ($460.80)
Business Hours 10 × m6i.xlarge 10hrs × 5 days $384.00 ~520 per instance ($998.40)

*Based on $0.192/hour per m6i.xlarge instance in us-east-1

What happened to EC2 Scheduled Reserved Instances?

AWS no longer sells them. Its CLI reference states that you can no longer purchase Scheduled Instances, and a September 3, 2024 update on the original announcement points to On-Demand Capacity Reservations for reserved capacity and Savings Plans for discounts. Neither turns instances off. For a recurring part-time pattern such as business hours, the current approach is to run regular On-Demand instances and schedule them to stop outside working hours.

Traditional Ways to Schedule EC2 (and Their Drawbacks)

Before introducing CloudAvocado solution, it’s worth noting how teams often handle EC2 scheduling using native AWS or DIY methods:

AWS-native schedulers: AWS offers two free options. Systems Manager Quick Setup Resource Scheduler schedules EC2 instances by tag from a console wizard. Instance Scheduler on AWS is a CloudFormation stack you deploy that also covers RDS, Aurora and Auto Scaling groups. Both pick instances by tag.

  • Pros:

    • Free, and maintained by AWS
    • Work across multiple accounts in an organization
  • Cons:

    • require non-trivial setup
    • someone need to maintain it
    • limited list of supported services

Custom Scripts or Lambda Functions: Some teams write their own AWS Lambda functions triggered by EventBridge schedules to stop and start instances.

  • Pros:

    • Effective
    • Gives more flexibility (and can even implement logic like “stop if CPU < 5% for 1 hour”)
  • Cons:

    • someone need to write code and maintain it, ensure that script runs in all target accounts/region

Manual Effort: The simplest (but least scalable) method is manually stopping instances via the AWS Console or CLI. I used this method long time ago.

  • Pros:

    • Effective
    • Free to use
  • Cons:

    • it’s easy to forget about it

Why look for an alternative? These methods either require engineering time to set up and maintain (infrastructure-as-code, scripting) or they rely on humans to click buttons. This is where CloudAvocado comes in – offering a user-friendly UI to automate instance scheduling without any custom scripts, in a matter of minutes.

Scheduling EC2 Instances in 5 Minutes with CloudAvocado

CloudAvocado is a cloud cost optimization tool for AWS, Google Cloud and Azure. One of its core features is automated scheduling of resources like EC2 (and RDS, etc.) to eliminate paying for idle time. We’ll see how to get started quickly and implement a smart schedule. No deep AWS expertise or coding required – perfect for DevOps engineers who want results fast.

1. Onboard Your AWS Account (No Scripts Needed)

To use CloudAvocado, you first connect it to your AWS environment. The good news: this setup is extremely simple and doesn’t involve running any scripts or agents on your side. CloudAvocado uses a secure cross-account role approach:

  • Sign Up & Connect: Sign up for a CloudAvocado account (a free trial is available). In the onboarding, you’ll be guided to create an AWS IAM Role with a predefined policy that grants CloudAvocado the minimal permissions it needs (like reading EC2 info and toggling start/stop). There’s no manual scripting – just follow the step-by-step instructions either with CloudFormation script or manual.

CloudAvocado immediately discovers your instances (and other resources, like ECS, EKS, RDS, etc.) in that account.

CloudAvocado’s platform is built for multi-account aggregation – you can easily view and schedule instances across dev, staging, and prod accounts all in one place. No more juggling AWS logins or switching regions manually.

2. Visualize Utilization with the Dashboard & Heatmaps

Once connected, CloudAvocado gives you a unified dashboard of your cloud usage and costs. Instead of combing through AWS Cost Explorer or CloudWatch metrics, you get a clear visual overview:

CloudAvocado’s dashboard provides a visual summary of your AWS costs and usage. Imagine merging CostExplorer and CloudWatch The intuitive UI includes charts (even heatmaps) highlighting usage patterns and potential waste. This makes it easy to identify idle periods at a glance.

  • Utilization Heatmaps: CloudAvocado includes visualizations that correlate when your instances are running (and how much they’re utilized). For example, you might see a weekly heatmap showing hours of high vs. low CPU utilization across your instances. These visuals quickly highlight that, say, CPU usage drops to near-zero every day after 7 PM – a strong indicator that the instance could be shut off at that time. By spotting dark “cold” areas on the heatmap (periods of low utilization), you identify scheduling opportunities immediately.
  • Metrics & Recommendations: The platform also presents charts of CPU and memory usage down to an hourly granularity, along with cost analytics. It can even highlight underutilized resources and suggest where you could save This approach helps build confidence that turning off an instance won’t disrupt anyone – you can literally see that it’s idle out-of-hours before you schedule it off.

Overall, with overwhelming amount of data from CloudWatch and CostExplorer – the UI is designed to remove as much noice as possible.

3. Define a Schedule (Idle-Aware Stop Times)

Now comes the core task: creating a schedule that will automatically stop and start your EC2 instances according to your desired timings. In CloudAvocado, this is done through a simple Schedules UI (no cron syntax needed):

  • Choose Off-Hours: Define the days and time ranges when instances should run, and when they should be shut down. For example, you might create a schedule named “Weekdays-9to5” that starts instances at 9:00 AM and stops them at 7:00 PM, Monday through Friday. You can specify time zone as needed. This covers turning them off on weeknights and all weekend.
  • Metric based schedule: A schedule Instead of a blunt stop at exactly 7:00 PM, you can configure an idle timeout after working hours– e.g. “stop if the instance has been idle for 60 minutes after 7:00 PM.”  People tent to work a bit shifted time, especially with remote work. This means if someone is using the instance past 7, the instance won’t be terminated mid-task. It will wait until the CPU drops below a threshold (set per instance, “Idle” is different for different resources) for set duration before shutting down.

This smart scheduling ensures you capture maximum savings without hurting productivity. You avoid the scenario of forgetting to turn off instances (wasting money), and avoid the risk of turning something off while it’s still needed. Everything is configurable in a few clicks.

4. Apply Schedules to Instances (or Automate with Tags)

After defining a schedule, you need to assign it to the target instances:

  • Direct Assignment: In the CloudAvocado Resources view, you can bulk-select the EC2 instances you want to schedule and simply apply your new schedule to them. For example, you might select all instances in the “Dev” environment group and apply the “Weekdays-9to7” schedule in one go. The UI clearly shows which resources have which schedule active.
  • Tag-Based Scheduling: For more convenient automation, CloudAvocado has custom AWS resource. Just assign CloudAvocado schedule tag to resources, with schedule id. This way, whenever a new instance with that tag appears, it will automatically inherit the appropriate schedule.
  • Multi-Account, Multi-Region: All of this works across multiple AWS accounts and regions seamlessly. If you’re a cloud engineer managing workloads for several teams or clients, you can view all their instances in CloudAvocado and apply schedules without having to log into each account separately. This aggregated view and control is a huge time-saver and prevents oversight.

Once a schedule is applied, CloudAvocado’s automation takes over. There’s no need to visit the AWS Console to start or stop instances manually – or to check if the schedule ran. You can always see the current state (running or stopped). And if you ever need to override (e.g. keep an instance running late just one night), you can disable schedule for “X amount of hours”

*  Create Teams and add Users (Optional)

CloudAvocado has role based access control, you can define different roles, assign resources to teams, etc.

Conclusion: Save Costs in Minutes – Give It a Try

Scheduling AWS resources is one of those quick wins in cloud cost optimization: it’s relatively easy to implement and brings significant savings (non-production resources bill for about 50 hours a week instead of 168). By using CloudAvocado, you can setup this process in couple minutes – without writing code or managing schedules by hand. As well – consider that it’s not just about EC2, CloudAvocado also schedules RDS (see how to schedule RDS instances), Auto Scaling groups, ECS, EKS, DocumentDB and MongoDB Atlas.  

What is AWS Artifact? Benefits and Overview

AWS Artifact is a crucial service for organizations navigating the complex landscape of cloud compliance and security. This comprehensive guide explores how AWS Artifact streamlines compliance management, enhances security measures, and supports businesses across various industries. Whether you’re new to AWS or an experienced user, this article offers valuable insights into leveraging AWS Artifact for your compliance needs.

What is AWS Artifact and Why is it Essential for Your Business?

AWS Artifact is Amazon Web Services’ premier portal for on-demand access to AWS compliance reports and agreements. This free service provides users with crucial security and compliance documents, helping organizations meet regulatory requirements and industry standards. As businesses increasingly migrate to the cloud, understanding and utilizing AWS Artifact becomes essential for maintaining a secure and compliant cloud environment.

The service offers two main categories of documents: AWS Artifact Reports and AWS Artifact Agreements. Reports include third-party audit reports, certifications, and attestations such as SOC reports, ISO certifications, and PCI DSS compliance reports. Agreements are legal documents that users can review, accept, and manage directly through the AWS Artifact portal, including NDAs and Business Associate Addendums for HIPAA compliance.

How Does It Fit into the AWS Ecosystem?

AWS Artifact is an integral part of Amazon Web Services comprehensive cloud platform. It works seamlessly with other AWS services to provide a holistic approach to cloud security and compliance. By offering direct access to compliance documentation, it complements services like AWS Security Hub and AWS Compliance Center, forming a robust framework for managing your organization’s compliance posture in the cloud.

Main Features

This service boasts several key features that make it an invaluable tool for compliance management:

  • On-demand access to compliance reports
  • Wide range of reports: certifications, attestations, audit reports (SOC, ISO, PCI, etc.)
  • Self-service portal for easy customer access
  • Security compliance across industries (healthcare, financial, etc.)
  • Regular updates to ensure access to the latest compliance information

How Can You Access and Use AWS Artifact?

Accessing AWS Artifact is a straightforward process through the AWS Management Console. Users can easily navigate the self-service portal to find, download, and manage the compliance documents they need. The user-friendly interface reduces the time and effort required to obtain critical compliance information, making it accessible even for those new to AWS services.

Key Benefits It Has to Offer

The benefits are substantial:

  • Time-saving: Immediate access to essential compliance documents
  • Enhanced transparency: Helps customers ensure AWS services meet their security and compliance requirements
  • Simplified audits: Streamlined process for compliance audits
  • Cost-effective compliance management: No additional cost for AWS customers
  • Global compliance support: Wide range of international certifications and standards

Different Industries Use Cases

AWS Artifact caters to a wide range of industries, each with its unique compliance requirements:

  • Healthcare: Provides essential documents for HIPAA compliance, including the Business Associate Addendum (BAA)
  • Financial Services: Offers SOC reports and PCI DSS compliance documentation
  • Government: Supports FedRAMP and other government-specific compliance needs
  • Global Businesses: Provides access to ISO certifications and region-specific compliance reports

Differences with Other Compliance Tools

While many compliance tools are available, AWS Artifact stands out for several reasons:

  • Direct source of AWS compliance documentation
  • Self-service access to reports and agreements
  • Integration with AWS account management
  • Regular updates to compliance documentation
  • No additional cost for AWS customers

How Does AWS Artifact Contribute to Overall Cloud Security?

While it primarily focuses on compliance documentation, it plays a significant role in cloud security. By providing detailed reports on AWS’s security controls and compliance measures, it helps organizations understand and verify the security posture of the AWS cloud. This transparency is crucial for businesses looking to build a secure cloud infrastructure and maintain the trust of their customers and stakeholders.

The Future of Compliance Management 

As cloud computing continues to evolve and regulatory demands increase, AWS Artifact is likely to play an even more critical role in compliance management. We can expect to see expanded document offerings, more industry-specific certifications, and enhanced integration with other AWS services. The future of AWS Artifact will likely focus on providing even more streamlined, automated compliance solutions to help businesses navigate the increasingly complex regulatory landscape.

Key Takeaways

  • Provides on-demand access to AWS compliance reports and agreements
  • Simplifies compliance management across various industries
  • Offers a user-friendly, self-service portal for accessing documents
  • Supports global compliance efforts with a wide range of certifications
  • Enhances transparency and builds trust in AWS cloud services
  • Streamlines the audit process and reduces compliance-related costs
  • Regularly updated to ensure access to the latest compliance information
  • Integrates seamlessly with other AWS services for comprehensive security and compliance
  • Crucial tool for organizations migrating to or expanding their presence in the cloud
  • Essential for building and maintaining a secure and compliant cloud environment

AWS Cost Anomaly Detection: A Complete Guide

In the ever-evolving landscape of cloud computing AWS Cost Anomaly Detection emerges as a powerful solution, offering organizations the ability to proactively monitor and control their cloud expenses. This comprehensive guide will explore how this innovative tool can revolutionize your approach to cloud financial management, helping you optimize spending and maximize the value of your AWS investments.

What is AWS Cost Anomaly Detection and Why Should You Care?

AWS Cost Anomaly Detection is a sophisticated feature within the AWS Cost Management suite that leverages machine learning to identify unusual spending patterns across your AWS accounts and services. By automatically analyzing historical cost data and establishing normal usage baselines, this tool can quickly flag potential issues before they escalate into significant financial concerns.

For businesses navigating the complexities of cloud environments, this capability is invaluable. It not only helps prevent unexpected budget overruns but also provides insights that can drive more strategic decision-making around resource allocation and optimization. Whether you’re a small startup or a large enterprise, understanding and implementing AWS Cost Anomaly Detection can be a game-changer for your cloud cost management strategy.

How Does AWS Cost Anomaly Detection Work Its Magic?

At its core, AWS Cost Anomaly Detection employs advanced machine learning algorithms to analyze your AWS spending patterns continuously. It establishes a baseline of normal usage by examining historical data and then monitors for any deviations from this established norm. When an anomaly is detected – such as a sudden spike in costs for a particular service or an unusual increase in overall spending – the system generates cost anomaly detection alerts based on user-defined preferences.

This proactive approach, utilizing cost anomaly detection alerts, allows organizations to respond swiftly to potential cost issues, investigating and addressing the root causes before they can significantly impact the bottom line. The system’s ability to learn and adapt over time means it becomes increasingly accurate in identifying true anomalies while reducing false positives.

Setting Up AWS Cost Anomaly Detection: A Step-by-Step Guide

Configuring AWS Cost Anomaly Detection is a straightforward process that can be completed through the AWS Management Console. Here’s a quick overview of the steps involved in setting up cost monitoring.

  1. Access the AWS Cost Management console and navigate to the Cost Anomaly Detection section.
  2. Choose your preferred detection method – either monitoring individual services or AWS services collectively.
  3. Set up alert subscriptions, defining who should receive notifications and through which channels (email or Amazon SNS).
  4. Define custom thresholds based on your typical spending patterns and risk tolerance.
  5. Review your settings and activate the anomaly detection feature.

Remember, the key to maximizing the benefits of this tool lies in ongoing management and fine-tuning. Regularly reviewing and adjusting your settings will ensure that the system remains aligned with your evolving cloud usage patterns and business needs.

What Types of Cost Anomalies Can You Detect?

AWS Cost Anomaly Detection is capable of identifying a wide range of unusual spending patterns, including:

  • Sudden spikes in overall AWS spending
  • Unexpected increases in costs for specific AWS services
  • Gradual but significant cost escalations over time
  • Unusual charges for rarely used resources

By casting a wide net, this tool helps ensure that no potential cost issue goes unnoticed, regardless of its nature or scale.

How Can You Leverage AWS Cost Anomaly Detection for Optimization?

Beyond its primary function of alerting you to potential cost issues, AWS Cost Anomaly Detection can be a powerful tool for ongoing cost optimization. By analyzing the patterns and insights provided by the system, you can:

  • Identify underutilized or forgotten resources that are unnecessarily driving up costs
  • Spot opportunities for rightsizing instances or adjusting reserved capacity
  • Detect and address misconfigurations that may be leading to inefficient resource usage, particularly in EC2 instances.
  • Gain a deeper understanding of your cost drivers, informing more strategic decision-making around resource allocation and enhancing cost visibility.

When used in conjunction with other AWS cost management tools like AWS Cost Explorer and AWS Budgets, Cost Anomaly Detection becomes part of a comprehensive strategy for maintaining optimal cloud spending.

What Are the Best Practices for Using AWS Cost Anomaly Detection?

To get the most out of AWS Cost Anomaly Detection, consider implementing these best practices:

  1. Start with conservative thresholds and adjust over time as you gain more insight into your normal spending patterns.
  2. Customize alert preferences to ensure the right people receive notifications through the most effective channels.
  3. Regularly review and analyze detected anomalies, such as cost anomalies, to identify recurring issues or areas for potential AWS cost optimization.
  4. Integrate Cost Anomaly Detection with other AWS cost management tools for a more comprehensive approach.
  5. Use cost allocation tags and cost categories to gain more granular insights into spending patterns across different projects or departments.

By following these practices, you can ensure that AWS Cost Anomaly Detection becomes an integral and effective part of your overall cloud financial management strategy.

Can AWS Cost Anomaly Detection Help with Budget Planning?

Absolutely! AWS Cost Anomaly Detection can be a valuable asset in the budget planning process, enhancing cost visibility. By providing insights into historical spending patterns and highlighting anomalies, it helps you:

  • Develop more accurate budget forecasts based on typical usage patterns
  • Identify seasonal trends or cyclical patterns in your AWS spending
  • Set more realistic budget thresholds for different services or accounts
  • Anticipate potential cost spikes related to product launches or other business events

When used in conjunction with AWS Budgets, Cost Anomaly Detection can help you create a more dynamic and responsive budgeting process that adapts to the ever-changing nature of cloud usage.

How Does AWS Cost Anomaly Detection Compare to Other Cost Management Tools?

While AWS Cost Anomaly Detection is a powerful tool in its own right, it’s important to understand how it fits into the broader ecosystem of AWS cost management tools:

  • AWS Cost Explorer: Focuses on visualizing and analyzing historical cost data, complementing the real-time anomaly detection capabilities.
  • AWS Budgets: Allows you to set predefined spending limits and receive alerts when costs approach or exceed these limits.
  • AWS Trusted Advisor: Provides broader recommendations for optimizing your AWS environment, including cost optimization suggestions.

Each of these tools has its strengths, and when used together, they form a comprehensive suite for managing and optimizing your AWS costs. Cost Anomaly Detection’s unique value lies in its ability to proactively identify unusual spending patterns that might be missed by more traditional budgeting and analysis tools.

What Challenges Might You Face with AWS Cost Anomaly Detection?

While AWS Cost Anomaly Detection is a powerful tool, it’s important to be aware of potential challenges:

  • False positives: Especially in environments with highly variable workloads, the system may occasionally flag normal cost fluctuations as anomalies.
  • Learning curve: Fine-tuning the detection models to suit your specific needs can take time and expertise.
  • Data lag: There can be a slight delay between when costs are incurred and when they’re reflected in the anomaly detection system.
  • Limited historical data: For new AWS accounts, the system may need time to accumulate enough data to establish accurate baselines.

Being aware of these potential issues can help you set realistic expectations and develop strategies to mitigate their impact.

How Can You Get Started with AWS Cost Anomaly Detection Today?

Ready to take control of your AWS costs? Here’s how you can get started with AWS Cost Anomaly Detection:

  1. Log into your AWS Management Console and navigate to the Cost Management section.
  2. Enable Cost Anomaly Detection if you haven’t already.
  3. Set up your first monitor, choosing between individual service monitoring or monitoring AWS services together.
  4. Configure your alert subscriptions, ensuring the right team members will receive notifications.
  5. Define your initial thresholds, starting conservatively and adjusting as you learn more about your typical spending patterns.
  6. Begin monitoring and analyzing the insights provided by the tool.

Remember, the key to success with AWS Cost Anomaly Detection is ongoing management and refinement. As you become more familiar with the tool and gain insights into your cloud spending patterns, you’ll be able to optimize its configuration to provide maximum value for your organization.

Key Takeaways

  • AWS Cost Anomaly Detection uses machine learning to identify unusual spending patterns in your AWS accounts.
  • It provides real-time alerts for potential cost issues, allowing for swift action to prevent budget overruns.
  • The tool can be customized to suit your specific needs and risk tolerance.
  • When used in conjunction with other AWS cost management tools, it forms part of a comprehensive cloud financial management strategy.
  • Regular review and fine-tuning of settings are crucial for maximizing the benefits of the tool.
  • Cost Anomaly Detection can provide valuable insights for budget planning and cost optimization efforts.
  • While powerful, the tool may face challenges such as false positives and data lag, which should be considered during implementation.
  • Getting started with AWS Cost Anomaly Detection is straightforward, but mastering its use requires ongoing effort and analysis.

By leveraging AWS Cost Anomaly Detection effectively, you can gain unprecedented control over your cloud costs, optimize your AWS spending, and ensure that your cloud investments deliver maximum value with minimal waste.

Updated pricing for Amazon EKS: Extended support explained

Earlier we talked about EKS at a high level in CloudAvocado article about EKS optimization. Here is real-life example: extended support for Amazon EKS. Among many other activities like monitoring cluster metrics, right-sizing nodes, and enabling autoscaling processes, surprisingly, Kubernetes version control is also important. Best practice: update Kubernetes on your EKS clusters to the latest available version once it’s released. Updates usually address security vulnerabilities, performance improvements etc., so it’s really important to check for a new versions once in a while. But not many of us did. However, that is has changed and now we need to pay more attention to it.

On April 1, 2024, Amazon announced general availability of extended support for versions of Kubernetes. It means from now on you can run your EKS clusters for up to 26 months from the date the version becomes available on EKS, instead of 14. Sounds good, however, this update produced a new pricing rule you need to know.

Standard EKS support

Kubernetes gets new features, design updates, and bug fixes with minor versions releases approximately once in four months. We already know that Amazon recommends creating new clusters using the latest version of Kubernetes and updating earlier created clusters to the latest version as well. The only thing you need to remember is that there are two support types now and the price of the cluster depends on it.

Each new Kubernetes version receives standard support for 14 months after being published on Amazon EKS.

Common billing rules are well known. You pay:

  • $0.10 per hour for each Amazon EKS cluster that you create
  • for services you use, as you use them (EKS on AWS using either EC2 you create to run your Kubernetes worker nodes or AWS Fargate)

What happens when it ends?

Amazon EKS

Extended EKS support

Immediately after the standard support term ends, Kubernetes version start receiving Extended support. It lasts for 12 more months. For example, standard support for version 1.23 in Amazon EKS ends on October 11, 2023. Extended support for version 1.23 began on October 12, 2023, and will end on October 11, 2024. It is available in all AWS regions. Exciting news – you don’t need to take any action to receive it – as soon as 14 months pass from the release date, clusters that still run it will be automatically onboarded to the extended support. 

New billing rules:

  • $0.60 (instead of $0.10) per hour for each Amazon EKS cluster that you create
  • for services you use, as you use them (EKS on AWS using either EC2 you create to run your Kubernetes worker nodes or AWS Fargate)

There are no limitations to Kubernetes in Amazon EKS extended support, so it won’t turn off or weaken your clusters’ capabilities. Clusters running Kubernetes versions released more than 26 months ago (14 months of standard support + 12 months of extended support) are upgraded to the oldest currently supported extended version automatically. It’s important to remember you still need to update cluster add-ons and Amazon EC2 nodes manually after the automatic control plane update, 

You can avoid auto-enrolling in extended support by upgrading your cluster to a Kubernetes version that’s still in standard support.

Standard vs extended EKS support: cost comparison

The price difference may not seem big at first sight. But let me prove that it’s worth your attention, especially if you use a lot of EKS. Simple calculations of monthly and full price differences between standard and extended support for one and more clusters: 

Clusters qty Standard support monthly cost

Extended support

monthly cost

Potential waste if not updated
1 month 12 month (full length)
1 730h * $0.1 = $73.0 730h * $0.6 = $438.0 $73.0 – $438.0 = – $365.0 – $4 380.0
10 $730.0 $4 380.0 – $3 650.0 – $43 800.0
30 $2 190.0 $13 140.0 – $10 950.0 – $131 400.0

As you can see, updating your clusters before they run into extended support can save you from spending an excessive $365 on each EKS cluster monthly! Real-life example: one of CloudAvocado’s users has 36 clusters, so in addition to monthly payment for included resources his extended support might have cost him 36 * $365.0 = $13 140.0 without any previous changes in the infrastructure. It’s good we were there to help.

You may assume it may be a big deal only for big organizations. However, I recommend setting up reminders regularly and updating Kubernetes versions before they run into extended support. Even if there are only a few clusters you can prevent unpredicted waste and keep your budget within limits.

Short FAQ

Will I get a notification when standard support is ending for Kubernetes version on my Amazon EKS? 

Yes, AmazonEKS sends a notification through the AWS Health Dashboard approximately 60 days before it ends

Are there any limitations to Kubernetes in extended support?

No, there are not.

Is AWS support available for clusters in extended support?

All clusters continue to have access to technical support from AWS.

Are there any limitations to patches for non-Kubernetes components in extended support?

Extended support will only provide support for AWS published Amazon EKS optimization AMIs for Amazon Linux, Bottlerocket, and Windows at all times. This means, you will potentially have newer components (such as OS or kernel) on your Amazon EKS optimized AMI while using Extended Support. 

Where can I update my Amazon EKS?  

Use this guide: Update existing cluster to new Kubernetes version

Does CloudAvocado help manage versions of EKS?

Yes, you’ll receive notifications about upcoming extended support while using the app and to your email to update them beforehand.

Follow my LinkedIn to learn more about interesting AWS updates that can help you avoid situations similar to those described above or book a Calendly meeting with me if you have questions about your AWS.

The Importance of Scheduling EC2 Instances on AWS: Beyond Cost to a Greener Future

EC2 scheduling is worth mentioning whenever we start talking about AWS cost optimization or carbon emissions. The reason is simple. Its not a secret that services like AWS’s Elastic Compute Cloud (EC2), has transformed the way businesses operate and became widely used resource for more than 1 million of users. But, with these advancements comes a responsibility to ensure that we’re using these resources wisely, especially for economic and environmental reasons.

Why EC2 scheduling is important?

To put it into perspective, think about your daily commute to work. Once you’ve parked your car, would you leave the engine running all day? Even if there were a hefty discount on fuel, would the cost savings justify the waste? Beyond the obvious financial folly, think about the unnecessary emissions and the depletion of a non-renewable resource.

In much the same way, leaving EC2 instances running when not in use, even if costs are managed, isn’t just wasteful — it’s environmentally irresponsible.

The Green Energy Argument

Many cloud providers, including AWS, are making commendable strides toward powering their massive data centers with renewable energy. On the surface, one might argue that if the power comes from green sources, then the environmental concern is negated. However, this view misses a crucial point.

Even if our cloud resources are powered by 100% green energy, there’s a cap on how much of this renewable energy is available at any given time. Every watt of green energy used to power idle EC2 instances is a watt that could have been used elsewhere.

Thus, by reducing our cloud resource consumption, we’re effectively freeing up green energy for use in other areas, accelerating the world’s transition to sustainable energy sources.

CO2 Emissions VS EC2 Scheduling

While it’s true that data centers powered by green energy significantly reduce their carbon footprint, our global transition to renewables is still in progress. Until that 100% green energy future is realized, every idle EC2 instance contributes to carbon emissions somewhere in the supply chain. Efficient usage of resources means reducing this footprint.

Efficient Cloud Management: A Broader Perspective

Adopting a sustainable approach to cloud computing extends beyond EC2:

  • Development Environments: These rarely need 24/7 uptime. Scheduling downtimes during off-hours can lead to substantial energy savings.
  • RDS: rarely stopped on development environments.
  • Batch Processing: If tasks run during specific hours, ensure instances are active only when needed.
  • Scalable Systems: AWS’s auto-scaling can match demand, ensuring you’re not over-provisioning resources.

Conclusion

The transformative potential of cloud computing is boundless. However, as we venture deeper into this digital age, it’s paramount that our steps are taken with consideration for our planet.

EC2 scheduling and adopting a mindful approach to resource usage is more than just an economic strategy — it’s a pledge toward a sustainable future. The less energy we consume in the cloud, the more renewable energy there is available to make a difference elsewhere. The next time you look at your EC2 dashboard, remember: it’s not just about the cost, but also the broader impact. Every instance, every watt, every decision counts. 

Top tools for AWS cloud cost optimization

Computing resources and business opportunities provided by cloud vendors like AWS are endless.  Amazon services can skyrocket your business growth and profitability. Yet, as any other system in the growing business, your AWS needs to be managed efficiently and optimized over time to improve productivity and cut expenses. Cloud computing has a dedicated set of practices for that goal, which is called cloud cost optimization. 

With the growth of cloud-based businesses and cloud consumption boost, the demand for cloud cost optimization tools is increasing. According to The Cloud Cost Management and Optimization Market Report for 2022-2029 companies like Harness, ParkMyCloud (Turbonomic), Virtana Optimize, Nomad, Kaseya Unigma, CloudZero, Flexera as well as many others have grown much in the past few years.  As the niche is growing and full of options, it may be difficult to choose the perfect AWS cloud cost optimization tool among all the available solutions. 

The main question is whether native AWS tools meet your needs, or whether you need a third-party tool. In this article, we’re going to tell you about both options based on the capabilities that are considered critical for cloud cost optimization.

Key cloud cost optimization capabilities

So which capabilities are crucial for cloud cost optimization? Here is the list: 

  • tagging
  • cost and utilization analytics
  • resource scheduling 
  • and of course, alerts for specific events or anomalies that can cause waste, if not managed properly (e.g. idle and overprovisioned resources)

These capabilities are key to efficient cloud cost management and there are several vendors currently available on the market that more or less cover all of these – including native AWS cost optimization tools. 

Native and third party cost optimization tools

There are many AWS cloud cost optimization tools to explore and allocate costs, as well as track and analyze cloud performance and resource utilization. While native tools seem like a natural choice, many companies find them insufficient for their business needs, or simply too cumbersome due to the need to pull data from multiple AWS tools to see the whole picture. In this case, businesses start looking for more robust and scalable all-in-one solutions.

Scheduling

Fact  – turning off your non-production instances on weekends and during non-business hours (e.g. 6pm-9am) can save you up to 70% of their cost. If not managed properly, your resources will waste a lot of your budget. So you need to schedule your test and development environments by setting AWS Instance Scheduler that will stop your  EC2 and Amazon RDS according to the provided timetable.

Skeddly is a valuable third-party tool designed to gain control over your expenses by efficiently managing the start and stop times of instances and virtual machines, helping you optimize resource usage and reduce costs. You can automate your backups and snapshots for instances, virtual machines, disks, and databases, while also removing outdated snapshots to minimize storage expenses. It also provides comprehensive IT automation capabilities, supporting a wide range of services like Amazon EC2, RDS and more. 

skeddly screenshot

Lots of cloud users can tell a lot about their positive experience with third party platform that has recommended itself as one of the top cloud cost management tools – ParkMyCloud (Turbonomic, recently acquired by IBM). Its so-called Parking Schedule Management was created to add timetables and assign them to required resources in order to use and pay for resources only when you need them.

parkmycloud screenshot

As ParkMyCloud is no longer supported, you might want to know that there is another solution of this kind called CloudAvocado. Its Scheduling capabilities are similar, and additionally, it enables tagging and utilization analytics in your environment to make cost management even more efficient.

cloudavocado aws scheduling screenshot

AWS tagging tools

Tagging is required for the allocation of your cloud costs. Cloud cost allocation is an activity that allows you to connect your AWS bill to specific parts of your product, features or organizational units. The process is straightforward – you assign tags as metadata to all resources to get required reports, analytics and insights per required cost object. Even previously mentioned Scheduling can become quite challenging without proper tagging, as you won’t be able to identify your non-production instances.

Native AWS tools that can help you add and manage your resources’ tags are Tag Editor and AWS Config Managed Rules. Some third-party platforms can also provide you with this functionality, however, you need to be sure the tool can work with your resources across all your accounts. This enables proper tagging across all your regions, projects, etc. and results in accurate and consistent cost allocation.

CloudAvocado works well for tagging also and can also help you to track your tagging progress and display all untagged resources.

untagged resources filter screenshot

Cost and utilization analytics

Your workload needs to be revisioned on a regular basis to detect under- or overprovisioned resources. The former occurs when the capacity of an instance is lower than the demand. It can cause productivity issues within the apps you develop. The latter can cause your cost to be wasted as demand is lower than the instance capacity. It means you can potentially save your budget by replacing it with smaller and cheaper instance/s. The process of matching your capacity to the demand at the lowest possible cost without sacrificing reliability is called rightsizing – and it’s one of the most critical yet complicated tasks in cloud optimization.  AWS provides the following tools to perform this task:

  • AWS Cost Explorer allows you to see patterns in AWS spending over time, project future costs, identify areas that may require your attention. You also should use it for detecting and deleting idle EC2 instances, Amazon RDS instances, Load Balancers and unassociated Elastic IP addresses.
  • AWS Cost and Usage Report provides you with data files that contain your detailed hourly AWS usage across accounts
  • AWS Compute Optimizer helps avoid overprovisioning and underprovisioning using utilization data for some AWS resources (EC2, EBS, ECS), services on AWS Fargate and AWS Lambda functions.
  • Amazon CloudWatch collects and tracks metrics
  • Amazon S3 Analytics – automated analysis and visualization of Amazon S3 storage patterns for cost-efficient tier management of your storage; you also can automate data lifecycle management with Amazon S3 Intelligent-Tiering and reduce Amazon S3 storage cost by identifying cost optimization opportunities with Amazon S3 Storage Lens.

screenshot with bar chart

In the case of third-party tools, some of them cover all the native AWS capabilities mentioned above in a single UI.  

For example, CloudAvocado can easily calculate your current monthly expenses, projected monthly cost and provide you with hourly CPU utilization breakdown for any instance, cluster or autoscaling group. AWS cost and utilization analytics are presented in dashboards and reports to help you make data driven decisions on scaling your workload according to the demand.

cloudavocado dashboard screenshot

Recommendations and alerts for events

Cloud cost optimization tools analyze your cloud usage and spending patterns to identify potential cost-saving opportunities. By providing recommendations, these tools help you react proactively to reduce unnecessary expenses, optimize resource allocation, and eliminate wasteful spending. This can lead to significant cost savings over time. 

AWS Trusted Advisor gathers potential areas for optimization for your workload and AWS Budgets triggers alerts when cost or usage exceeds (or is forecasted to exceed) a budgeted amount.

Among many other mentioned functionalities, CloudAvocado has built-in recommendations that highlight different cases of unoptimized usage: idle, unscheduled, untagged resources and resources that produce waste due to over-provisioning.

recommendations screenshot

The verdict

Effective cloud cost optimization is essential for maximizing profitability. Since choosing the right tool can be challenging due to the variety of options available, it’s important to focus on the critical capabilities required for AWS cost optimization first. Look for cost allocation, resource scheduling, and alerts for identifying wasteful spending, and always remember that cost optimization is an ongoing process. 

To get more information about AWS cloud cost optimization tools usage read our article cloud cost optimization checklist.

Or simply sign up for a free CloudAvocado trial to start your AWS cost optimization: get analytics on your AWS spendings, efficiency, and potential savings.