Provider
Octopus DeployIncident detail
AWS deployments failing when using service role for EC2 instance
Timeline window
to
Get alerted the next time Octopus Deploy breaks
Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.
Timeline
Incident updates
Every update on the official status source, oldest to newest, exactly as it appeared there.
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
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
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.
Resolved
This incident has been resolved.
Keep exploring
More from Octopus Deploy
Neighboring incidents on Octopus Deploy's timeline and the rest of their record on OutageDeck.