Skip to content
OutageDeck

Incident detail

S3 endpoints for keys with special characters broken

S3 endpoints for keys with special characters broken

Resolved incidentMinor1 affected service

Timeline window

to

Timeline

Incident updates

Updates are normalized from the official source chronology so timeline changes remain easy to scan.

  1. 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.

  2. Identified

    A likely mitigation has been identified and we are discussing the proper implementation method.

  3. Identified

    We have implemented a PR rollback to mitigate this issue. We will actively monitor its progress

  4. 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.