#terraform-aws-modules - May 2024

Hey! 👋 I have a question about this ECR module. It seems to enforce the idea that the lifecycle policy should be based on number of images in the repository (default: 500) rather than the number of days an image has hung around for, even though ECR supports both types of policies. Is that a conscious decision by-design, or an oversight? If by-design, is that because it’s a widely accepted best practice? Looking for either sources I can read or just a quick summary on why it’s the way it is please!

Hey everyone, could anyone help me with aws-team-roles module? 😅
How can I change the name format for the roles, that are generated by that module? For example, I'm getting a team role like this:

  # aws_iam_role.default["admin"] will be created
  + resource "aws_iam_role" "default" {
...
      + name                  = "nsp-gbl-dns-admin"

But I'm trying to use the name format 'namespace-tenant-environment-stage' - and when I run terraform in the org account, it wants to assume role nsp-core-gbl-dns-terraform. And fails %)

I've found out, that if I set var.label_order to

      - namespace
      - tenant
      - environment
      - stage 

Then it works fine.

Is this the correct solution? Or I'm trying to do something backwards?

Hello,
https://github.com/cloudposse/terraform-aws-ec2-autoscale-group/commit/aa3840ee7874a74c27e4226eaab585fab9501faf#diff-dc46acf24af[…]1f33d9bf2532fbbR1

With the data , terraform plan no longer works if subnets don’t exist (which can happen when an entire infrastructure has to be created from scratch)

Would you have an idea for solving this problem?

hey there, I’m looking at the aws-config module and I’m running into a few issues:

• I’m using an organization aggregator
• I’m using a central SNS topic and S3 bucket
• I see resources in my child accounts showing up in the aggregators for my central account
• i do not see configuration change events for my child accounts (configuration change timeline) in the central aggregator
• I do see configuration change events in the configuration timeline on the child accounts
• I do not see anything actually touching the central sns topic?
is this expected? Am I not supposed to see configuration timeline / change events in the central account? Should I see activity on the sns topic?

Hi guys, there seems to be an issue with the VPC component - would it be possible to update the version of dynamic-subnet within it, so we can use ap-southeast-4 Melbourne?
Details are here - https://github.com/cloudposse/terraform-aws-components/issues/1047