Incident report 29/01/2024
Start: Bilbo/1.16.0 - 10:49am
End: Conan/2.0.0 - 11:14am
Reach: limited to flows using AWS services
Impact: high - blocking
Description
Section titled “Description”During the deployment of the Conan release, we encountered a bug impacting specific workflows that incorporate AWS integration.
AWS services undergo regular updates to enhance functionality and security. A key enhancement scheduled for the Conan release aimed at extending support for the latest AWS server instances.
This document briefly details the cause, resolution, and subsequent actions to be taken. The Mindflow team apologizes for the inconvenience and extends thanks to our client’s team for their support and understanding.
Causes
Section titled “Causes”- The issue was promptly identified during this incident: the sequence of servers within the AWS integration’s internal service definition had been altered. As a result, certain AWS step services attempted to connect to the wrong AWS server instances.
Resolution
Section titled “Resolution”- Upon receiving the report, the Mindflow team quickly pinpointed the issue and reverted the AWS server definitions to their correct order. The impact was confined to workflows utilizing AWS services that were executed within the timeframe of the incident.
Follow-up
Section titled “Follow-up”- The Mindflow development team will examine and enhance the server update process for all integrations to ensure seamless transitions without any disruptions.