HCP Terraform Workspace Runs Failing with IAM Errors After AWS Provider Upgrade
Jul 29, 12:36 UTCJul 29, 20:44 UTC
Duration
8h 8m
Impact
Major
Root cause
Not disclosed
HashiCorp, 90 days
13 incidents
Affected
Not listed by the vendor.
Final update
Our Engineering team has pulled v6.57.0 of the AWS provider from the registry and published a fixed v6.57.1.
Timeline
- Resolved · Jul 29, 20:44 UTC
Our Engineering team has pulled v6.57.0 of the AWS provider from the registry and published a fixed v6.57.1.
- Monitoring · Jul 29, 16:50 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.
- Identified · Jul 29, 16:08 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.
- Identified · Jul 29, 12:56 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.
- Investigating · Jul 29, 12:36 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.
More from HashiCorp
Full historyHCP Boundary Scheduled Maintenancelasted 7mHCP Terraform – Elevated 502 Bad Gateway Errorslasted 1h 51mGitHub and Other VCS workloads experiencing intermittent issueslasted 2h 45mTerraform Runs Failinglasted 22mHCP Vault Azure: Cluster Updates and Creationlasted 5d 6hUsers unable to access releases.hashicorp.conlasted 57m