Most teams start with a simple goal: turn off staging at night, bring it back in the morning.
Then one engineer needs an exception. Another team shares the same environment. Someone forgets to re-enable a resource after a demo. And before long, you’re managing a mix of custom scripts, Slack reminders, and “don’t touch this until Monday” calendar events.
One of our latest releases removes that extra work without creating new things to maintain.
What’s new
EC2 schedule agent (pre-shutdown actions)
Define your pre-shutdown steps: drain connections, flush logs, send notifications. They run inside CloudAvocado, so there’s nothing extra to maintain.
Per-resource schedule pause
When a specific resource needs to stay on (a demo next week, a long-running test), pause its schedule for a set period. CloudAvocado re-enables it automatically when the time is up.
Autotagging
Tag a resource once, and CloudAvocado assigns it to the right schedule and team automatically. New resources get picked up without any setup steps.
Multi-team users
Users can now belong to multiple teams, each with its own permissions. Useful when engineers work across environments or when ownership of a resource is shared.
Why it matters: fewer scripts to babysit, fewer missed exceptions, and scheduling rules that stay consistent as teams grow.
How to get started
If you’re already using scheduling in CloudAvocado, these features are available now, no migration needed.
New to scheduling in CloudAvocado? Start by defining your working hours, apply them via tags or per resource, and add pre-shutdown actions where needed.
It’s all available via our Free trial, or Book a demo if you’d like to see how it works.
