[here]

Closes #158

Bumps aws-actions/configure-aws-credentials from @v3 (Node 16) to @v6 (Node 24) in terraform-plan.yaml and terraform-apply.yaml. Nothing else changes; the inputs in use (role-to-assume, role-session-name, aws-region) are unchanged across v3→v6.

Before merging

• Terraform plan (OIDC) ran on this PR and the configure-aws-credentials step succeeded
• Posted plan shows no resource changes

Heads up: merging triggers Terraform apply (OIDC) against the production account (workflow files match the **/*.yaml path filter).

After merge

• Confirm the apply run succeeded with no changes
• Comment on Bump aws-actions/configure-aws-credentials from v3 to v6 in incubator's Terraform workflows #158 with links to the plan and apply runs

[github-actions]

Terraform plan in terraform
With backend config files: terraform/prod.backend.tfvars

No changes. Your infrastructure matches the configuration.

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.

✅ Plan applied in Terraform apply (OIDC) #111