← Back to Supabase History
minor✓ Resolved

S3 endpoints for keys with special characters broken

Supabase•
Status
resolved
Duration
54m
Updates
4
Coverage
0 articles

INCIDENT TIMELINE

✓ Resolved
This incident has been resolved.
resolved
This incident has been resolved. A recent API Gateway deployment altered how certain special characters in S3 object key paths were encoded before reaching storage, causing signature verification failures (403) for affected requests. The change has been reverted and issue is now fixed.
identified
We have implemented a PR rollback to mitigate this issue. We will actively monitor its progress
identified
A likely mitigation has been identified and we are discussing the proper implementation method.
identified
We have identified an issue where S3 endpoints for keys with special characters will be broken. We are actively investigating the correct mitigation for this issue.

📊 TECHNICAL DETAILS

Internal ID
081503eb-aa7d-4a9e-b5a9-7815a01b2da7
External ID
5cbt09m9y46n
🕐 Started
🔄 Last Updated
✓ Resolved
MINOR
Impact Level
54m
Total Duration
4
Status Updates
Affected Components
Storage
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we request generation of one.
0 / 100 requests100 more needed