Octopus incident

AWS deployments failing when using service role for EC2 instance

Major Resolved View vendor source →

Octopus experienced a major incident on January 8, 2024, lasting 31d 7h. The incident has been resolved; the full update timeline is below.

Started
Jan 08, 2024, 09:22 PM UTC
Resolved
Feb 09, 2024, 05:03 AM UTC
Duration
31d 7h
Detected by Pingoru
Jan 08, 2024, 09:22 PM UTC

Update timeline

  1. investigating Jan 08, 2024, 09:22 PM UTC

    We're investigating AWS deployment failures for customers upgraded to 2024.1.6245 and are using the "AWS service role for an EC2 instance" option, which throw the error "An account identifier was not found". For more details of the issue and a possible workaround see the Github issue https://github.com/OctopusDeploy/Issues/issues/8551

  2. identified Jan 08, 2024, 10:44 PM UTC

    We have found a likely cause of this issue and are working on a fix. In the meantime, please refer to the Github issue for more updates - https://github.com/OctopusDeploy/Issues/issues/8551

  3. monitoring Jan 09, 2024, 04:03 AM UTC

    We have implemented a fix in v2024.1.6809 which will be rolling out to cloud customers over the next two days. If you need the fix in your cloud instance sooner, please contact https://octopus.com/support. We will continue to monitor for any further issues.

  4. resolved Feb 09, 2024, 05:03 AM UTC

    This incident has been resolved.