Choose API key rotation for a planned credential change in a Node.js customer support backend; choose revocation when active abuse makes continued access unacceptable. The deciding constraint is whether the old credential may remain usable while legitimate workers migrate. A support access review needs that decision in writing, particularly when the reviewer must also sign off on which workload incurred the bill.
TL;DR: Rotation preserves traffic through a grace window. Revocation stops access immediately and can break callers. During a known leak, accepting downtime is the containment decision; rotating alone leaves the attacker access during the grace window. When uncertainty spans the fleet, rotate for legitimate callers and revoke the specific credential known to be exposed.
Containment comes first.
Decision record: preserve attribution through the credential change
The proposed architecture treats credential continuity and billing attribution as separate invariants.…