Test storage credentials with application-referenced uploads

When validating Supabase Storage credentials after a database copy, select an application record whose saved media URL points to the target project, then test a signed GET for that exact object. Arbitrary bucket-list samples can select copied metadata whose underlying files remain in the source project. Successful listing or HeadObject does not establish that file contents are readable, and NoSuchKey from those samples does not establish a credential failure. Verify record provenance and URL origin before treating failed samples as a rollout blocker. Successful samples prove only those downloads, not bucket-wide completeness.

Applies when: Database copies and original uploads coexist in Supabase storage metadata. Keywords: Supabase S3 storage metadata cloned database credentials signed downloads provenance