S3 endpoints for keys with special characters broken

Resolved

Started

Lasted 54m

View official incident ↗

Updates

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

  2. Identified

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

  3. Identified

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

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