I've heard of it happening to colleagues twice in the last three years (though it has doubtless happened more frequently than that) - I think that last time was because they were requesting some ancient instance type that AWS is probably phasing out.