Skip to main content
Octopus Deploy

AWS deployments failing when using service role for EC2 instance

Partial outage Lasted 31d 7h · started · Octopus Deploy's page

Level
confirmed
Worst impact
Partial outage
Down Index
33of 100

What to do

  • Check whether your product depends on Octopus Deploy. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 31d 7h it lasted.

    Anything that failed between 2024-01-08 21:22 UTC and 2024-02-09 05:03 UTC may need a replay.
  • Subscribe to Octopus Deploy's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=octopus works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Octopus Deploy 4

  1. investigating

    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

    provider

  2. identified

    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

    provider

  3. monitoring

    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.

    provider

  4. resolved

    This incident has been resolved.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-ed1c53fdea

Is Octopus Deploy still down?

No, this incident was resolved 2024-02-09 05:03 UTC. For Octopus Deploy's live state, see https://down.guide/octopus.

How long did it last?

31d 7h, from 2024-01-08 21:22 UTC to 2024-02-09 05:03 UTC, by the times Octopus Deploy posted.

What caused it?

Octopus Deploy hasn't published a root cause. If it does, it shows here.

Where does this come from?

Octopus Deploy's official status page, https://status.octopus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.