HashiCorp incident
HCP Terraform Workspace Runs Failing with IAM Errors After AWS Provider Upgrade
HashiCorp experienced a minor incident on July 29, 2026 affecting HCP Terraform, lasting —. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 29, 2026, 12:36 PM UTC
Status: Investigating 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. Affected components HCP Terraform (Partial outage)
- identified Jul 29, 2026, 12:56 PM UTC
Status: Identified 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. Affected components HCP Terraform (Partial outage)
- identified Jul 29, 2026, 04:08 PM UTC
Status: Identified 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. Affected components HCP Terraform (Partial outage)
- monitoring Jul 29, 2026, 04:50 PM UTC
Status: Monitoring 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. Affected components HCP Terraform (Partial outage)
- resolved Jul 29, 2026, 08:44 PM UTC
Status: Resolved Our Engineering team has pulled v6.57.0 of the AWS provider from the registry and published a fixed v6.57.1. Affected components HCP Terraform (Operational)