Old servers survive because something on them runs at 2 a.m. Finding every Windows Task Scheduler job, SQL Server Agent job and crontab entry, and moving them to EventBridge Scheduler with Lambda, ECS tasks or Step Functions, with retries, alerts and an audit trail they never had.
When a decommissioning project stalls, the reason is often a scheduled job: an export to a bank, a nightly sync, a report emailed at 6 a.m. These jobs run on the server nobody wants to touch, under an account nobody remembers, and fail silently when they fail.
Book a free 30-minute call. You'll leave knowing what we'd do first and roughly what it costs, whether or not you hire us.
Windows: export Task Scheduler tasks from every server, including the account each runs as.
SQL Server: list SQL Server Agent jobs and their steps; many call SSIS packages, scripts or other servers.
Linux: every user's crontab plus /etc/cron.* and systemd timers.
Record what each job does, what it touches and who notices if it stops.
EventBridge Scheduler handles one-time and recurring schedules in any time zone, with retries and dead-letter queues, and can call hundreds of AWS service APIs directly. The first 14 million invocations a month are free and it costs $1.00 per million after that, so nightly jobs cost effectively nothing.
Once a month: what changed in tech that month and what it means for you, from cloud and AI to security and the tools you build with. Every item links to its source. No sales pitch, unsubscribe in one click.
Book a free 30-minute call about it. Bring your setup and your bill; you'll leave knowing what we'd do first and roughly what it costs, whether or not you hire us.
Or keep reading
Postgres Connection Limits on RDS: What 1,600 Simultaneous Connections Do, With and Without RDS Proxy
db.m7g.large allows 832 connections. When 1,600 clients connected at once, 916 were refused; through RDS Proxy all 1,600 succeeded, with the slowest waiting 12 seconds. The measurements at 100, 400, 800 and 1,600, the errors you'll see, and what a fresh AWS SDK client per request does under the same burst.
Read
Lambda Web Functions vs Event Functions: Where the New Model Saves Money, and Where It Doesn't
Web Functions bill active CPU and held memory; Event Functions bill wall-clock time multiplied by memory. For AWS's own three example workloads, classic Lambda at 512 MB is cheaper. Once requests spend seconds waiting (LLM streaming, slow APIs, long polls) Web Functions win by 40 times or more: a 10-second stream costs about $3 per million requests instead of $134. The arithmetic, the crossover and a checklist.
Read
As of October 25, 2026. Provided as is, for general information, and accurate to the best of our knowledge on the date shown. Not legal, compliance, tax, financial or other professional advice. Prices, limits and vendor services change; check current vendor documentation before relying on anything here. Terms of use.