Make Multipart Upload Abort Idempotent Before Orphaned Parts Start Billing You

Short summary

Multipart upload abort can succeed in object storage while the HTTP response is lost, leaving the database thinking the upload is active and orphaned parts accruing charges. Model abort as a state transition with durable intent and an idempotency key, use an outbox for reliable delivery, and reconcile NoSuchUpload responses to distinguish already-aborted from completed uploads. Post-abort verification that parts are gone is correctness, not optional housekeeping.

• •Model abort as a state machine (active→aborting→aborted) with durable intent and idempotency keys, not a direct SDK call
• •Reconcile NoSuchUpload responses: only 'already absent because abort succeeded' may converge to aborted
• •Post-abort part verification is required correctness; lifecycle cleanup is a backstop, not a substitute for reconciliation

Generated with AI, which can make mistakes.