403 error when trying to access Autoops in newly created serverless projects

Summary

403 error when trying to access Autoops in newly created serverless projects

We resolved the issue affecting AutoOps at 12:30 UTC. Elastic Cloud Hosted and Elastic Cloud Serverless: Customers who created a new account in the AWS us-east-1 region since approximately 00:30 UTC on October 22, 2026 were unable to access AutoOps and may have seen an error (HTTP 403) when opening it.

• Started

  Oct 22, 2026 · 11:19 AM

• Resolved

  Oct 22, 2026 · 8:50 PM

• Duration

  9h 30m

• Severity

  Major

• ◐

  Investigating

  Oct 22 · 11:19 AM Elastic

  We are investigating an issue affecting AutoOps for newly created accounts in the AWS us-east-1 region. Accounts created after 00:00 UTC on October 22, 2026 may be unable to access AutoOps and may see an error (HTTP 403) when opening it. Elastic Cloud Hosted: AutoOps is not available for affected new accounts. Elastic Cloud Serverless: AutoOps is not available for affected new accounts. Existing deployments and projects, and all other Elastic Cloud functionality, are not affected. Our engineering teams are working to identify the cause and restore access. We will provide the next update within 60 minutes, or sooner if there is a significant change

• ◆

  Identified

  Oct 22 · 12:00 PM Elastic

  We have identified the cause of the issue affecting AutoOps and are deploying a fix. Elastic Cloud Hosted and Elastic Cloud Serverless: Customers who created a new account in the AWS us-east-1 region since approximately 00:30 UTC on October 22, 2026 were unable to access AutoOps and may have seen an error (HTTP 403) when opening it. The fix is rolling out now, and we expect the situation to be fully resolved by 13:00 UTC. Existing deployments and projects, and all other Elastic Cloud functionality, are not affected.

• ✓

  Resolved

  Oct 22 · 8:50 PM Elastic

  We resolved the issue affecting AutoOps at 12:30 UTC. Elastic Cloud Hosted and Elastic Cloud Serverless: Customers who created a new account in the AWS us-east-1 region since approximately 00:30 UTC on October 22, 2026 were unable to access AutoOps and may have seen an error (HTTP 403) when opening it.