Can anyone explain why when I launch a new T2.micro instance, it occasionally (perhaps 1 in 50) starts with a CPU credit balance of zero, instead of the 30 it is meant to have?
I've attached screenshots of the CPU credit balances from two machines I launched nearly simultaneously from an Autoscaling group.
It isn't a massive deal, but it is upsetting my monitoring system to see near-zero cpu credits!