Update Terraform cloudposse/ec2-autoscale-group/aws to v0.43.1 (main)

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/ec2-autoscale-group/aws (source)	module	minor	0.40.0 → 0.43.1

---

Release Notes

cloudposse/terraform-aws-ec2-autoscale-group (cloudposse/ec2-autoscale-group/aws)

v0.43.1

Compare Source

🚀 Enhancements

fix cpu_options condition @​arnoldasbrazys (#​162)

what

Should fix:

• Error: Attempt to get attribute from null value
• This value is null, so it does not have any attributes

why

• Not providing Optional cpu_options should not break the module

references

• Closes #​161

v0.43.0

Compare Source

add cpu_options to launch template @​y3ti (#​159)

what

Add new variable cpu_options to specify CPU options for an Amazon EC2 instance

why

I need to disable Intel Hyper-Threading for instances created by AutoScaling Group. EC2 and Launch Template provides a CPU Options configuration that allows for:

• disable Intel Hyper-Threading Technology by setting threads_per_core to 1 (default is 2 which means that hyper threading is enabled)
• define cpu cores per instance (you might do this to potentially optimize the licensing costs of your software with an instance that has sufficient amounts of RAM for memory-intensive workloads but fewer CPU cores)
• enable AMD Secure Encrypted Virtualization-Secure Nested Paging (AMD SEV-SNP) - a CPU feature that provides the following properties like attestation and memory encryption

references

https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/launch_template#cpu-options
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-optimize-cpu.html
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/sev-snp.html

v0.42.0

Compare Source

feat: cleartext user_data variable @​nitrocode (#​158)

what

• feat: cleartext user_data variable

why

• Saves us from needing to base64 encode this input
• I vendored this module as a component and the YAML catalog's userdata needed to be base64 encoded. I could have done this using gomplate's base64 encoding function in the yaml but it wouldn't look as nice so I thought a new input would be handy here so we can defer the b64 encoding to terraform instead

vendor.yaml

apiVersion: atmos/v1
kind: AtmosVendorConfig
metadata:
  name: vendor-config
  description: Atmos vendoring manifest
spec:
  # More upstream components can be found here github.com/cloudposse-terraform-components
  sources:
    - component: "ec2-autoscale-group"
      source: "github.com/cloudposse/terraform-aws-ec2-autoscale-group?ref=v{{.Version}}"
      version: "0.41.1"
      targets:
        - "components/terraform/{{.Component}}"
      excluded_paths:
        - "**/.git*"
        - "**/examples"
        - "**/test"
        - "**/*.yaml"
        - "**/LICENSE"
        - "**/README.md"

stack yaml

    ec2-autoscale-group/kali:
      metadata:
        component: ec2-autoscale-group
        inherits:
          - ec2-autoscale-group/defaults
      vars:
        enabled: true
        name: kali
        # ...
        user_data: |
          #!/bin/bash
          set -xe

          # Install updates and packages
          sudo apt-get update -y
          sudoapt-get upgrade -y

          # Install AWS SSM Agent
          wget https://s3.amazonaws.com/ec2-downloads-windows/SSMAgent/latest/debian_amd64/amazon-ssm-agent.deb
          sudo dpkg -i amazon-ssm-agent.deb
          sudo systemctl status amazon-ssm-agent
          sudo systemctl enable amazon-ssm-agent
          sudo systemctl start amazon-ssm-agent

references

N/A

v0.41.1

Compare Source

fix: remove deprecated `elastic_gpu_specifications` @​RoseSecurity (#​154)

what

Amazon Elastic Graphics died on 8 Jan 2024, and the AWS provider yanked the knob in v6.0.0. Use GPU-class instance types (G4*/G5, etc.) or other modern accelerators instead.

What

• Resolves the following error in pipeline:

│ Error: Unsupported block type
│ 
│   on .terraform/infra/modules/autoscale_group/main.tf line 39, in resource "aws_launch_template" "default":
│   39:   dynamic "elastic_gpu_specifications" {
│ 
│ Blocks of type "elastic_gpu_specifications" are not expected here.

---

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Testing

• Validated with atmos validate stacks
• Performed successful atmos terraform plan on component using this module

References

• EOL Announcement

🤖 Automatic Updates

Fix go version in tests @​osterman (#​152)

what

• Update go 1.24

why

• Error loading shared library libresolv.so.2 in Go 1.20

References

• https://sweetops.slack.com/archives/G014YEKDH4K/p1746672149263629
• https://github.com/golang/go/issues/59305#issuecomment-1488478737
• https://github.com/cloudposse/terraform-aws-cloudfront-s3-cdn/pull/294/#issuecomment-2859195553

Replace Makefile with atmos.yaml @​osterman (#​151)

what

• Remove Makefile
• Add atmos.yaml

why

• Replace build-harness with atmos for readme genration

References

• DEV-3229 Migrate from build-harness to atmos

v0.41.0

Compare Source

add max_healthy_percentage - option used during instance refresh @​scott-doyland-burrows (#​149)

what

This is adding the max_healthy_percentage option.

This allows the instance refresh to set this value.

min_healthy_percentage is already set as an option.

why

The option is currently missing from the terraform module.

references

https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/autoscaling_group#max_healthy_percentage

fix: Terratest Account ID @​milldr (#​150)

what

• Remove old account ID check from tests

why

• Account ID has changed. We shouldnt use the account ID to check

references

• https://github.com/cloudposse/terraform-aws-ec2-autoscale-group/pull/149

🤖 Automatic Updates

Migrate new test account @​osterman (#​148)

what

• Update .github/settings.yml
• Update .github/chatops.yml files

why

• Re-apply .github/settings.yml from org level to get terratest environment
• Migrate to new test account

References

• DEV-388 Automate clean up of test account in new organization
• DEV-387 Update terratest to work on a shared workflow instead of a dispatch action
• DEV-386 Update terratest to use new testing account with GitHub OIDC

Update .github/settings.yml @​osterman (#​147)

what

• Update .github/settings.yml
• Drop .github/auto-release.yml files

why

• Re-apply .github/settings.yml from org level
• Use organization level auto-release settings

references

• DEV-1242 Add protected tags with Repository Rulesets on GitHub

Update .github/settings.yml @​osterman (#​146)

what

• Update .github/settings.yml
• Drop .github/auto-release.yml files

why

• Re-apply .github/settings.yml from org level
• Use organization level auto-release settings

references

• DEV-1242 Add protected tags with Repository Rulesets on GitHub

Update .github/settings.yml @​osterman (#​145)

what

• Update .github/settings.yml
• Drop .github/auto-release.yml files

why

• Re-apply .github/settings.yml from org level
• Use organization level auto-release settings

references

• DEV-1242 Add protected tags with Repository Rulesets on GitHub

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[mergify]

/terratest

[Igor Rodionov (goruha)]

/terratest