v1.526.0

feat(kms): updates with embedded policy creation - part2 @Gowiem (#1136)

## what

• Updates the KMS module to support embedded policy creation

why

• This allows for easy wiring in of aws-team-role roles into the KMS policy, so we do something like "Admins in the dev account have access to use this Key"

references

• This is a continuation of PR #523 which I could not continue as I no longer have access to push to Cloud Posse except as a fork 😢
  • @nitrocode did a great review with some solid suggestions in #523. I have completed my work from that review as part of this newer PR.

Update Changelog for `1.524.0` @github-actions (#1179)

Update Changelog for [`1.524.0`](https://github.com/cloudposse/terraform-aws-components/releases/tag/1.524.0)

v1.525.0

• No changes

v1.524.0

Announce code freeze @goruha (#1178)

## what * Announce code freeze on readme

why

• Readme is more informative than issue (while issue will be emailed)

references

• #1177

Update Changelog for `1.523.1` @github-actions (#1176)

Update Changelog for [`1.523.1`](https://github.com/cloudposse/terraform-aws-components/releases/tag/1.523.1)

v1.523.1

feat(elasticache-redis): add snapshot retention limit @nitrocode (#1171)

## what

• add snapshot retention limit

why

• Resolves ElastiCache.1 (ElastiCache (Redis OSS) clusters should have automatic backups enabled) securityhub control by giving the ability to set this value to a number greater than 0

references

• Default is 0 https://github.com/cloudposse/terraform-aws-elasticache-redis/blob/9104d9a6a120ae9c90f59c5eb4ea711cc2d2c6bb/variables.tf#L223-L227
• Module received the feature 5 years ago so no need to update the module version cloudposse/terraform-aws-elasticache-redis#45
• Related PR #1170 which upgrades the module

🤖 Automatic Updates

Update Changelog for `1.523.0` @github-actions (#1174)

Update Changelog for [`1.523.0`](https://github.com/cloudposse/terraform-aws-components/releases/tag/1.523.0)

v1.523.0

feat: Support `enabled` flag for EKS Storage Classes @milldr (#1173)

## what - Add support for enabled flag in storage class variables

why

• Create option to disable a given storage-class if it's include in an imported default component catalog

references

• n/a

v1.522.0

🚀 Enhancements

feat(elasticache-redis): add engine input for valkey support @nitrocode (#1170)

## what

• add engine input for valkey support

why

• Valkey is far cheaper than redis

Notes

• Design options
  1. Add a new key to local.cluster_attributes and add a variable to the component, default it to redis, and pass as an argument to the module as-is
     • We could shy away from the pattern to using engine = var.engine in the local.
  2. Allow var.redis_clusters to supply engine with a default for redis and pass to module as-is
  3. Same as option 2 but allow local.cluster_attributes to overwrite it
     • This might be best of both worlds however no other argument does this so it would be breaking the pattern
• Went with option 2 so the argument isn't a new requirement for everyone and it doesn't break consistency

references

• https://github.com/cloudposse/terraform-aws-elasticache-redis/releases/tag/v1.7.0
• https://aws.amazon.com/blogs/opensource/why-aws-supports-valkey/
• https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/elasticache_replication_group#engine
• hashicorp/terraform-provider-aws#39641
• https://github.com/hashicorp/terraform-provider-aws/releases/tag/v5.73.0
• https://docs.aws.amazon.com/AmazonElastiCache/latest/dg/Clusters.Create.html
• https://www.lastweekinaws.com/blog/aws-valkey-play-when-a-fork-becomes-a-price-cut/

v1.521.0

[eks/spacelift-worker-pool], [eks/spacelift-worker-pool-controller] Initial commit @Nuru (#1168)

## what

• [eks/spacelift-worker-pool] Initial commit
• [eks/spacelift-worker-pool-controller] Initial commit

why

• Support deployment of the Kubernetes Operator for Spacelift Worker Pools to an EKS cluster

[dns-delegated] Fix README.md to remove suggestion of deploying regionally @Nuru (#1167)

## what

• Remove suggestion from README that it can be deployed regionally
• Add details and references about using dns-delegated and dns-primary

why

• Old information was wrong and lacking in detail, causing confusion

fix: Runs-On README @milldr (#1166)

## what - Remove unclosed / unused summary

why

• This is breaking the cloudposse/docs release pipelines

references

• https://github.com/cloudposse/docs/actions/runs/11380845724

v1.520.0

[vpc] Add `max_nats` configuration @Nuru (#1158)

## what

• [vpc] Add max_nats configuration

why

• Allow budget-conscious users (e.g. test environments) to use fewer NAT gateways

v1.519.0

fix: Frontmatter for `run-ons` @milldr (#1156)

## what - Update frontmatter in runs-on module

why

• Correct tags

references

• https://github.com/cloudposse/docs/actions/runs/11278466395/job/31366989761

Update Changelog for `1.517.1` @github-actions (#1154)

Update Changelog for [`1.517.1`](https://github.com/cloudposse/terraform-aws-components/releases/tag/1.517.1)

v1.518.0

• No changes