# OIDC AWS Deployment Failures

- Provider: [env0](https://down.guide/env0)
- Level: confirmed
- Impact: Degraded
- lasted 0m
- started 2026-03-10 10:00 UTC
- Managed Deployment Workers, Self-Hosted Deployment Workers
- id: DWN-27747697e7
- Official page: https://status.env0.com/incident/cmmktzx2i0clok5jdbqyvial9

## Updates from env0
### 2026-03-10 10:00 UTC: resolved
Type: Incident
 Duration: 1 hour and 15 minutes
 Affected Components: Managed Deployment Workers, Self-Hosted Deployment Workers
 Mar 10, 11:15:00 GMT+0 - Resolved - The issue affecting OIDC-based AWS deployments has been resolved. All systems are operating normally. No data was lost or compromised. We apologize for the inconvenience. Mar 10, 11:00:00 GMT+0 - Monitoring - A fix has been deployed for OIDC-based AWS deployment failures. We are monitoring to confirm full recovery. Customers using access keys or non-AWS providers were not affected. If you continue to experience issues, contact \[support@env0.com\](mailto:support@env0.com). Mar 10, 10:20:00 GMT+0 - Identified - We have identified the root cause of the OIDC AWS deployment failures. A recent platform update introduced a change that is incompatible with some AWS IAM OIDC identity provider configurations. Our team is working on a fix. Mar 10, 10:00:00 GMT+0 - Investigating - We are investigating reports of failed AWS deployments for customers using OIDC-based authentication. Our team is actively looking into this.

---
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://sazabi.com/?utm_source=down-guide&utm_medium=markdown).