Mexico’s technology capital and a nearshore engineering hub for US companies. Mexico City teams often run non-production environments in both us-east-1 and local regions, creating cross-border scheduling complexity.
Those teams run AWS RDS in non-production the same way everyone does: around the clock, used only during the America/Mexico_City working day. Relational Database Service instances bill every hour they exist, and most of those hours in Mexico City are nights and weekends nobody is working.
The RDS idle problem in Mexico City
RDS instances typically bill in the range of $100-2,000/mo per instance, and in a non-production account the meter runs whether or not anyone is logged on. Scheduling RDS to Mexico City working hours removes the hours you were never using.
How ZopNight helps
ZopNight schedules RDS to stop outside Mexico City hours, flags the oversized and idle ones, and reports the result against real usage. It ships 490 built-in audit rules across AWS (216), GCP (127), and Azure (147), starts read-only, and excludes production by default. See it on AWS EC2 and the discipline in FinOps.
How ZopNight schedules RDS
The loop that does this is deliberately mechanical, and it starts read-only. You connect your cloud provider with a read-only role, and ZopNight discovers every RDS across your regions and accounts. It records a per-action permission verdict for each one, so you can see where it can list a resource but not yet stop it, and you review that inventory, filter it by status or type, and search for the specific resources you care about before anything is scheduled.
Scheduling itself is a cron you write once in plain terms, stop at 7 PM, start at 8 AM on weekdays, pinned to your timezone so the jobs fire at local business hours rather than UTC. A weekly 24-hour grid shows the schedule visually so you catch gaps and overlaps before you save, and an estimate of active versus inactive hours appears before you commit. Resources attach individually or bundle into groups like “dev-cluster” or “staging-db” so a whole environment follows one cadence.
Actions run in dependency order, so a database comes up before the app server that depends on it. When something needs to stay up, an override forces a RDS ON or OFF for a defined window, carries a reason so teammates understand why it exists, and expires automatically so nothing is left running by accident. If a start or stop fails, ZopNight retries up to three times and falls back to a dead-letter queue rather than silently dropping the action, and every state change lands in an audit trail that records whether a schedule, an override, or a specific user triggered it.
Getting started
Getting started is intentionally low-stakes:
- Connect your cloud provider with a read-only role. Nothing is scheduled or changed at this stage.
- Let ZopNight discover your RDS and review exactly what it found, filtered by account, region, and status.
- Create a schedule in your timezone and attach the non-production resources or groups you want it to cover.
- Watch the first cycle run, with Slack, Teams, or Google Chat notifications on every start, stop, and failure, then layer in idle cleanup and guided rightsizing.
Production stays excluded by default throughout, and because discovery and recommendations are read-only, you can prove the value before you enable a single action.
Questions we get a lot.
If yours isn't here, email us and we'll answer directly.
Does scheduling RDS use Mexico City local time?
Yes. Schedules run in your timezone, around Mexico City working hours.
Will this affect production?
No. Production is excluded by default; only the non-production RDS resources you choose are scheduled.