#terraform - August 2025

hi
so the 0.18.1 release of https://github.com/cloudposse/terraform-aws-acm-request-certificate caused some sudden breakage for me, because we were pinning to minor version (~>0.18.0)
but the readme got me thinking, for terraform modules does it not make sense to accept patch versions in the same way as you would with libraries?
(as an aside it is pre-1.0 so I think the patch number doesn't really get used as such in semver, but with the cadence of that module (0.18.0 was last year) it kind of feels like it should be 1.x.x anyway)

Hi. Im running the tgw/spoke component after running the vpc component and this block of hcl is erroring out

data "aws_vpc" "default" {
  for_each = module.this.enabled && var.create_transit_gateway_vpc_attachment && var.config != null ? var.config : {}
  id       = each.value["vpc_id"]
}

with the error

Error: no matching EC2 VPC found
│
│   with module.tgw_spoke_vpc_attachment.module.standard_vpc_attachment.data.aws_vpc.default["platform-sandbox"],
│   on .terraform/modules/tgw_spoke_vpc_attachment.standard_vpc_attachment/main.tf line 38, in data "aws_vpc" "default":
│   38: data "aws_vpc" "default" {

the vpc was created successfully and there is a default vpc as well

Join us for "Office Hours" every Wednesday 01:30PM (PST, GMT-7) via Zoom.

This is an opportunity to ask us questions on terraform and get to know others in the community on a more personal level. Next one is Aug 13, 2025 01:30PM.

👉️ Register for Webinar

#office-hours (our channel)

So I'm going to ask, what I consider, a weird question. Half the org wants to use atmos and the other half wants "native" terraform. I'm think something like Atlantis or Spacelift would be a way of bridging the gap. With that being said, I'm also certain Atlantis would be preferred for cost reasons. Is there an available POC with Atlantis deployed to EKS?

v1.13.0-rc1
1.13.0-rc1 (August 06, 2025)
NEW FEATURES:

The new command terraform stacks exposes some stack operations through the cli. The available subcommands depend on the stacks plugin implementation. Use terraform stacks -help to see available commands. (#36931)

ENHANCEMENTS:


Filesystem functions are now checked for consistent results...

v1.14.0-alpha20250806
1.14.0-alpha20250806 (August 06, 2025)
ENHANCEMENTS:


terraform test: expected diagnostics will be included in test output when running in verbose mode" (#37362)


terraform test: ignore prevent_destroy attribute during when cleaning up tests" (<a href="https://github.com/hashicorp/terraform/issues/37364"...

Join us for "Office Hours" every Wednesday 01:30PM (PST, GMT-7) via Zoom.

This is an opportunity to ask us questions on terraform and get to know others in the community on a more personal level. Next one is Aug 20, 2025 01:30PM.

👉️ Register for Webinar

#office-hours (our channel)

Curious if anyone else has worked with the terraform-aws-efs module and tried using an Access Point enforcing the optional root directory creation but not using the optional user identity.

It seems to me that this module does not make them optional if you want to use access points, which makes the module unusable if you dont want one or the other features which are both independently optional as far as AWS EFS goes.

v1.14.0-alpha20250813
1.14.0-alpha20250813 (August 13, 2025)
ENHANCEMENTS:


terraform test: expected diagnostics will be included in test output when running in verbose mode" (#37362)


terraform test: ignore prevent_destroy attribute during when cleaning up tests" (<a href="https://github.com/hashicorp/terraform/issues/37364"...

Heads up, the HashiCorp releases have been too noisy, so I've just disabled them.

Join us for "Office Hours" every Wednesday 01:30PM (PST, GMT-7) via Zoom.

This is an opportunity to ask us questions on terraform and get to know others in the community on a more personal level. Next one is Aug 27, 2025 01:30PM.

👉️ Register for Webinar

#office-hours (our channel)

Any idea why i get this error when trying to create a lambda? I have filename specified so it shouldn't trigger s3_key
Error: Missing required argument
│
│ with module.lambda.aws_lambda_function.this[0],
│ on .terraform/modules/lambda/main.tf line 40, in resource "aws_lambda_function" "this":
│ 40: s3_key = var.s3_key
│
│ "s3_key": all of s3_bucket,s3_key must be specified

Raising Feature Request for supporting custom rules · Issue #131 · cloudposse/terraform-aws-config

Join us for "Office Hours" every Wednesday 01:30PM (PST, GMT-7) via Zoom.

This is an opportunity to ask us questions on terraform and get to know others in the community on a more personal level. Next one is Sep 03, 2025 01:30PM.

👉️ Register for Webinar

#office-hours (our channel)

Hi, this commit which impacts among other things cloudposse's vpc_endpoints (super nice!) module pinned the aws' provider version to <6.0.0 which kind of broke our templates. Does anybody know if this was intentional, and if so is there an upgrade on the roadmap?

Hi! I found a bug in the ECS cluster module. It's creating IAM instance profiles when I'm only defining Fargate capacity. I fixed it with this PR: https://github.com/cloudposse/terraform-aws-ecs-cluster/pull/71

Hi everyone,
I’m currently working on the Atmos and components upgrade. I have upgraded each component from the Cloudposse individual component repo. However, when I try to run terraform plan for a component, I’m getting the following error:

The remote state has role_arn: null, but Terraform reports it as an invalid configuration.

Has anyone encountered this issue before? Any guidance on how to resolve it would be greatly appreciated.

Planning failed. Terraform encountered an error while generating this plan.
Error: Invalid backend configuration
│
│   with module.allowed_role_map.module.account_map.data.terraform_remote_state.data_source[0],
│   on .terraform/modules/allowed_role_map.account_map/modules/remote-state/data-source.tf line 54, in data "terraform_remote_state" "data_source":
│   54:   config   = lookup(local.ds_configurations, local.ds_backend, local.backend)
│
│ The given configuration is not valid for backend "s3": unexpected attribute "role_arn".
╵
╷
│ Error: Invalid backend configuration
│
│   with module.iam_roles.module.account_map.data.terraform_remote_state.data_source[0],
│   on .terraform/modules/iam_roles.account_map/modules/remote-state/data-source.tf line 53, in data "terraform_remote_state" "data_source":
│   53:   config   = lookup(local.ds_configurations, local.ds_backend, local.backend)
│
│ The given configuration is not valid for backend "s3": unexpected attribute "role_arn".
╵
 Error
exit status 1