OIDC AWS Deployment Failures

What to do

• Check whether you use env0 Managed Deployment Workers, Self-Hosted Deployment Workers. 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 0m it lasted.

  Anything that failed between 2026-03-10 10:00 UTC and 2026-03-10 10:00 UTC may need a replay.

• Subscribe to env0's feed to hear about the next one first. RSS feed

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

Updates from env0 1

1. resolvedMar 10, 2026, 10:00 AM UTC

   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.

   provider

Corrections

None so far.

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