#refarch - August 2023

https://github.com/cloudposse/terraform-aws-ecs-alb-service-task is now failing with the error in the screenshot.

this is used in a component based on the refarch ecs-service.

hey guys, any idea how I can add a CMK to the cloudwatch logs that get created by cloudposse/rds/awswhen specifying values for the enabled_cloudwatch_logs_exports variable?

AWS teams integration is working in terms of adding the values, but the billing admin can't see anything in billing. Is something off here?

these are from refarch directly (don't think there are any customizations): https://github.com/cloudposse/terraform-aws-components/tree/main/modules/aws-sso

billing RO

      "arn:${local.aws_partition}:iam::aws:policy/AWSBillingReadOnlyAccess",
      "arn:${local.aws_partition}:iam::aws:policy/AWSSupportAccess",

billing admin

      "arn:${local.aws_partition}:iam::aws:policy/job-function/Billing",
      "arn:${local.aws_partition}:iam::aws:policy/AWSSupportAccess",

The Spacelift admin stack needs this fix: https://github.com/cloudposse/terraform-aws-components/issues/771.

The component updater is trying to go from 1.259.0 to 1.278.0 and it fails consistently.

Quick PR https://github.com/cloudposse/terraform-aws-components/pull/819

Anyone know how to address this TGW error?

╷ │ Error: creating EC2 Transit Gateway VPC Attachment: DuplicateTransitGatewayAttachment: tgw-0550c8f9754f4c11e has non-deleted Transit Gateway Attachments with same VPC ID. │ status code: 400, request id: 0292a4de-a29e-4c78-b2c4-b00f525346c1 │ │ with module.tgw_spoke_vpc_attachment.module.standard_vpc_attachment.aws_ec2_transit_gateway_vpc_attachment.default["plat-ue1-beta"], │ on .terraform/modules/tgw_spoke_vpc_attachment.standard_vpc_attachment/main.tf line 43, in resource "aws_ec2_transit_gateway_vpc_attachment" "default": │ 43: resource "aws_ec2_transit_gateway_vpc_attachment" "default" {

Quick PR: https://github.com/cloudposse/terraform-aws-nlb/pull/45

So we are overhauling our AWS tagging and wanted to know, generally speaking what the level of effort might be to say add a namespace to cloudposse’s tags. Thinking something like “cp:stage”, “cp:environment” etc.. Also want to normalize all our tags to lower case. PS: where might a change like this be accomplished? My impression is that it’s handled by the terraform-null-label, but I could be mistaken.

FYI: the atmos updater keeps creating PRs for spacelift/admin-stack, but it is a bad update: https://github.com/cloudposse/terraform-aws-components/issues/771.

That needs to be addressed otherwise it will break the module.

Quick PR: https://github.com/cloudposse/terraform-aws-components/pull/829

So when creating spacelift spaces, I was trying to get another layer for stage under the space for tenant..

Here's an odd issue.. So I am trying to update Spacelift's root admin stack, but am getting an error:

🧵 Thoughts on S3 bucket grants adding direct support for the canonical user? Currently the owner is set in the core s3-bucket component, but the grant requires an id that isn't dynamic.

Hi all,
in terraform-aws-ecs-cloudwatch-autoscaling i was trying to add step_scaling_policy_configuration i am getting error of An argument named "scaling_adjustment" is not expected here.
Interval 1: 2 to 2.5
Interval 2: 2.5 to 3
Interval 3: 3 to 5
Interval 4: 5 and above
expecting help on this..