Ambra incident

InteleShare Incident

Minor Resolved View vendor source →

Ambra experienced a minor incident on June 9, 2025 affecting Web Services and Image Processing and 1 more component, lasting 1h 16m. The incident has been resolved; the full update timeline is below.

Started
Jun 09, 2025, 04:05 PM UTC
Resolved
Jun 09, 2025, 05:21 PM UTC
Duration
1h 16m
Detected by Pingoru
Jun 09, 2025, 04:05 PM UTC

Affected components

Web ServicesImage ProcessingImage Viewing

Update timeline

  1. investigating Jun 09, 2025, 04:05 PM UTC

    We have received reports of issues on the InteleShare platform. Engineering teams are currently investigating. Additional information will be provided as soon as it is available.

  2. monitoring Jun 09, 2025, 04:29 PM UTC

    An issue has been identified where AWS calls were failing, leading to issues with viewing studies within InteleShare. Our Engineering teams have engaged AWS support at this time, and viewing of studies are beginning to recover. We are continuing to monitor the situation.

  3. resolved Jun 09, 2025, 05:21 PM UTC

    The incident has been resolved and service is back to normal levels. Our team will be conducting a root cause analysis and sharing as soon as possible. We will continue to monitor the situation to ensure there are no further issues.

  4. postmortem Jun 09, 2025, 06:56 PM UTC

    **Issue Summary:** An automated update intended to modify a permissions policy encountered an unexpected failure. Instead of performing an in-place update, the process attempted to remove and then recreate the policy. While the removal was successful, the creation step failed, resulting in a missing policy until manual intervention restored it. **Impact:** During this period, newly launched instances and existing instances with expired cached permissions began experiencing errors when attempting to access necessary data. This led to intermittent issues in viewing and ingesting studies. **Resolution & Next Steps:** The issue was promptly identified and corrected through manual intervention. To prevent recurrence, we are actively reviewing and enhancing our processes to ensure that permissions policies are updated atomically and in-place. This improvement will strengthen system reliability and minimize the risk of disruption.