# AWS deployments failing when using service role for EC2 instance

- Provider: [Octopus Deploy](https://down.guide/octopus)
- Level: confirmed
- Impact: Partial outage
- lasted 31d 7h
- started 2024-01-08 21:22 UTC
- id: DWN-ed1c53fdea
- Official page: https://stspg.io/hxgkqywnjtbd

## Updates from Octopus Deploy
### 2024-01-08 21:22 UTC: 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

### 2024-01-08 22:44 UTC: 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

### 2024-01-09 04:03 UTC: 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.

### 2024-02-09 05:03 UTC: resolved
This incident has been resolved.

From the builder: does your app depend on Octopus Deploy? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=octopus) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention Octopus Deploy.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-ed1c53fdea), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.