HashiCorp incident

HCP Terraform Workspace Runs Failing with IAM Errors After AWS Provider Upgrade

Resolved after 8 hours 7 minutes, affecting HCP Terraform, on July 29, 2026.

resolved Jul 29, 2026, 08:44 PM UTC

Our Engineering team has pulled v6.57.0 of the AWS provider from the registry and published a fixed v6.57.1.

Started
Jul 29, 2026, 12:36 PM UTC
Resolved
Jul 29, 2026, 08:44 PM UTC
Duration
8h 7m
Detected by Pingoru
Jul 29, 2026, 12:36 PM UTC

Affected components

HCP Terraform

Update timeline

  1. investigating Jul 29, 2026, 12:36 PM UTC

    We are aware of and investigating reports of degraded performance after AWS provider update. Our team is working to identify and resolve the issue. We will post updates with more information as it becomes available.

  2. identified Jul 29, 2026, 12:56 PM UTC

    Our Engineering team has identified the cause and we are actively working on a fix. A workaround would be to pin the aws provider to v6.56.0 till the fixed patch is released. Once we have additional information, we will share another update.

  3. identified Jul 29, 2026, 04:08 PM UTC

    Our Engineering team has identified the cause and we are actively working on a fix to publish a patch version of v6.57.1 and pull v6.57.0 from the registry. Prior to that we advise working around the issue by pinning the AWS provider to v6.56.0. Once we have additional information, we will share another update.

  4. monitoring Jul 29, 2026, 04:50 PM UTC

    Our Engineering team has pulled v6.57.0 of the AWS provider from the registry, and continue to work to publish v6.57.1. We will continue to monitor for failures.

  5. resolved Jul 29, 2026, 08:44 PM UTC

    Our Engineering team has pulled v6.57.0 of the AWS provider from the registry and published a fixed v6.57.1.

Your product runs on more than HashiCorp

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →