Terraform AWS Provider v6.59.0 , errors during plan for aws_network_acl_rule resources
Aug 13, 17:50 UTCAug 13, 19:06 UTC
Duration
1h 16m
Impact
Minor
Root cause
Not disclosed
HashiCorp, 90 days
13 incidents
Affected
Not listed by the vendor.
Final update
Our Engineering team has resolved the issue. We released the Terraform AWS Provider v6.60.0 with a fix. Affected systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team.
Timeline
- Resolved · Aug 13, 19:06 UTC
Our Engineering team has resolved the issue. We released the Terraform AWS Provider v6.60.0 with a fix. Affected systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team.
- Identified · Aug 13, 17:50 UTC
Our engineering team has identified the cause of the "Missing Resource Identity After Read" errors and has completed a fix. We are preparing version 6.60.0 of the Terraform AWS Provider, which includes this fix. v6.60.0 is not yet available in the registry. This affects `aws_network_acl_rule` resources that were created with provider versions earlier than 6.39.0. Terraform runs that do not manage `aws_network_acl_rule `resources are unaffected. Users encountering errors can continue running Terraform by pinning the provider to version 6.58.0: ``` terraform { required_providers { aws = { source = "hashicorp/aws" version = "6.58.0" } } } ```
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