Upgrade terraform AWS provider

[devksingh4]

Summary by CodeRabbit

Chores

• Upgraded AWS provider to version 6.18.0 across production and quality assurance environments.

[github-actions]

💰 Infracost report

Monthly estimate generated

_{This comment will be updated when code changes.}

[coderabbitai]

Walkthrough

AWS Terraform provider version bump from 6.17.0 to 6.18.0 across production and QA environments. Updates version constraints in main.tf configuration files and corresponding provider hashes in .terraform.lock.hcl lock files.

Changes

Cohort / File(s)	Change Summary
Production Environment terraform/envs/prod/main.tf, terraform/envs/prod/.terraform.lock.hcl	AWS provider version constraint updated from ~> 6.17.0 to ~> 6.18.0; provider hashes replaced with new set corresponding to 6.18.0 release.
QA Environment terraform/envs/qa/main.tf, terraform/envs/qa/.terraform.lock.hcl	AWS provider version constraint updated from ~> 6.17.0 to ~> 6.18.0; provider hashes replaced with new set corresponding to 6.18.0 release.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

• Verify AWS provider 6.18.0 release is legitimate and compatible
• Confirm hash values match official provider release signatures
• Check that no other provider constraints or dependencies were inadvertently affected

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The PR title "Upgrade terraform AWS provider" directly and accurately describes the primary change in the pull request. The changeset consistently updates the AWS Terraform provider from version 6.17.0 to 6.18.0 across both the production and QA environments, modifying both .terraform.lock.hcl and main.tf files. The title is concise, clear, and avoids vague language or noise; it communicates to a reviewer scanning git history exactly what the change is about without being overly verbose or missing essential context.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch dsingh14/update-terraform

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

Cache: Disabled due to data retention organization setting

Knowledge base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between 2f9bf91 and 5947a83.

📒 Files selected for processing (4)

• terraform/envs/prod/.terraform.lock.hcl (1 hunks)
• terraform/envs/prod/main.tf (1 hunks)
• terraform/envs/qa/.terraform.lock.hcl (1 hunks)
• terraform/envs/qa/main.tf (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: Run Unit Tests
• GitHub Check: Build Application

🔇 Additional comments (4)

terraform/envs/prod/main.tf (1)

5-5: Version constraint update is correct.

The change from ~> 6.17.0 to ~> 6.18.0 properly allows patch-level updates while preventing unintended minor version jumps. Ensure the lock file is also updated before applying.

terraform/envs/qa/main.tf (1)

5-5: Version constraint updated consistently with production.

This change mirrors the prod environment upgrade, maintaining version parity across environments.

terraform/envs/qa/.terraform.lock.hcl (1)

28-51: Lock file updated consistently with QA main.tf constraint.

The hashes match the production environment lock file (both using 6.18.0), ensuring consistent provider versions across environments.

terraform/envs/prod/.terraform.lock.hcl (1)

28-51: No action required; lock file was correctly regenerated.

AWS provider v6.18.0 is a legitimate release, and the lock file changes are expected. When a lock file is generated with terraform init, it contains the signatures of all available releases for that provider version. These hashes are automatically validated every time you run terraform init or terraform plan.

The hashes in the lock file (both h1 and zh formats) were correctly regenerated when the provider constraint was updated. Manual offline verification of hashes is not necessary—Terraform will validate them automatically during initialization and planning against the Terraform Registry.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}