Planning for the Day the Credits Run Out

Credit running out is not an emergency. It is a date you can calculate in the first week and plan around. The reason it feels like an emergency is that almost nobody does the calculation.

Establish the burn rate

Run a representative workload for a few days, then look at the daily charge in the billing console. That figure, not a guess, is your burn rate.

Divide the remaining balance by the daily figure and you have an exhaustion date. Compare it with the credit expiry date and take whichever comes first. That is the date that matters.

Watch how the rate moves

Burn rate is rarely flat. It rises as you add environments and as data accumulates in storage. Recalculate every couple of weeks rather than trusting the first number, because storage in particular only ever grows.

Decide what happens at zero, before zero

There are three honest options, and choosing deliberately is what separates a plan from a scramble:

• Continue on your own payment method. Requires the account to be on a paid footing rather than a trial that halts. See what upgraded means.
• Scale down to a sustainable baseline. Decide now which environments are essential and which are conveniences.
• Migrate or stop. Legitimate for a time-boxed project, provided data extraction is planned rather than improvised.

Set alerts against the date, not just the amount

Budget alerts usually trigger on spend. Add calendar reminders at two weeks and one week before your projected exhaustion date. Spend alerts tell you the rate; a date reminder tells you the deadline.

Reduce the rate before you need to

The changes that extend a runway are the same ones worth making anyway:

• Shut down non-production environments outside working hours.
• Delete detached volumes and old snapshots.
• Release reserved addresses that are not attached to anything.
• Right-size machines that were provisioned generously, using measured figures.

Keep the data safe regardless

Whatever the plan, make sure the data can leave. If exhaustion means the environment stops, an untested export is the thing you will regret. Verify a restore while you still have a running system to restore into.