v0.41.0 Unstable Pre-Release

We are revising and standardizing our handling of security groups and security group rules across all our Terraform modules. This is an early attempt with significant breaking changes. We will make further breaking changes soon, so using this version is not recommended.

feat: use security-group module instead of resource @SweetOps (#166)

what

• use security-group module instead of resource

why

• more flexible than current implementation
• bring configuration of security group/rules to one standard
• bump minimal required terraform version to 0.14

references

• CPCO-409

v0.40.0

added `autoscaling:SetInstanceProtection` permission to default aws iam policy @vmonrabal (#180)

what

• Add the autoscaling:SetInstanceProtection to the aws iam policy

why

• We need to protect the instances from scale in when they are processing data and the mentioned permission was missing in the default policy

references

• https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-instance-termination.html#instance-protection

v0.39.1

🚀 Enhancements

fix always dirty aws_security_group.default @RomanNess (#170)

Fixes #148.

I tested the fix in a project that uses the module.
Though, I was too lazy to checkout this repo and did the changes in the web editor. I hope that I did not mess up the formatting.

v0.39.0

Add scheduled_actions variables (#174) @florian0410 (#177)

What is changing ?

Adding a new var scheduled_actions to give ability to setup beanstalk Scheduled actions.

Example:

scheduled_actions = [
  {
    name            = "Refreshinstances"
    minsize         = "1"
    maxsize         = "2"
    desiredcapacity = "2"
    starttime       = "2015-05-14T07:00:00Z"
    endtime         = "2016-01-12T07:00:00Z"
    recurrence      = "*/20 * * * *"
    suspend         = false
  },
  {
    name            = "Refreshinstances2"
    minsize         = "1"
    maxsize         = "2"
    desiredcapacity = "2"
    starttime       = "2015-05-14T07:00:00Z"
    endtime         = "2016-01-12T07:00:00Z"
    recurrence      = "*/30 * * * *"
    suspend         = false
  }
]

Why ?

We cannot use additional_settings to define these since it does not handle the dedicated resource field.

https://github.com/cloudposse/terraform-aws-elastic-beanstalk-environment/blob/2d146afbe6ca491d07b81732209244867bbdcd5c/variables.tf#L380-L385

https://github.com/cloudposse/terraform-aws-elastic-beanstalk-environment/blob/2d146afbe6ca491d07b81732209244867bbdcd5c/main.tf#L867-L875

references

• About resource setting field: https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/elastic_beanstalk_environment#resource
• closes #174

v0.38.1

🚀 Enhancements

chore: adds note to README about call for maintainer @Gowiem (#178)

what

• Adds searching for maintainer callout to README description

why

• This repo is somewhat neglected since most contributors / the Cloud Posse team don't use Beanstalk, so looking for a maintainer will hopefully get it more attention / usage.

v0.38.0

Update service role policy @anton-kachurin (#175)

what

Adds a new variable prefer_legacy_ssm_policy to be able to control IAM policy attached to the service role.

why

As mentioned in #171 , the AWSElasticBeanstalkService policy is getting deprecated and AWS recommends to replace it with AWSElasticBeanstalkManagedUpdatesCustomerRolePolicy. Since existing environments may still rely on permissions existing in the deprecated policy, the prefer_legacy_ssm_policy variable's default value is set to true for backward compatibility.

references

Closes #171

v0.37.2

🤖 Automatic Updates

Update Terraform cloudposse/route53-cluster-hostname/aws to v0.12.0 @renovate (#163)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/route53-cluster-hostname/aws (source)	terraform	minor	0.10.1 -> 0.12.0

---

Release Notes

cloudposse/terraform-aws-route53-cluster-hostname

v0.12.0

Compare Source

context.tf updated to v0.24.1, minimum required Terraform version bumped to 0.13.0 when needed, readme updated @​maximmi (#​35)

#### what - update context.tf to v0.24.1 - minimum required Terraform version bumped to 0.13.0 - readme updated, Bridgecrew compliance badges added #### why - It allows for setting the letter case of tag names and labels, back compatibility with context v0.22.0 and below - we have dropped support for Terraform 0.12 - To be able see and fix the recommendations from Bridgecrew so we can position our modules as standards compliant

v0.11.0

Compare Source

minimum required Terraform version bumped to 0.13.0, context.tf updated, readme updated @​maximmi (#​34)

#### what - update context.tf to v0.23.0 - minimum required Terraform version bumped to 0.13.0 - readme updated, Bridgecrew compliance badges added #### why - It allows for setting the letter case of tag names and labels - we have dropped support for Terraform 0.12 - To be able see and fix the recommendations from Bridgecrew so we can position our modules as standards compliant

v0.37.1

🚀 Enhancements

Update alb_zone_id of some missing regions @cereme (#137)

what

• Append alb_zone_id map for missing regions.

why

• Using unsupported regions(eu-north-1, etc..) fails with Error: Invalid index (See #136)

references

• closes #136

v0.37.0

context.tf updated to v0.24.1, minimum required Terraform version bumped to 0.13.0 when needed, readme updated @maximmi (#164)

what

• update context.tf to v0.24.1
• minimum required Terraform version bumped to 0.13.0
• readme updated, Bridgecrew compliance badges added

why

• It allows for setting the letter case of tag names and labels, back compatibility with context v0.22.0 and below
• we have dropped support for Terraform 0.12
• To be able see and fix the recommendations from Bridgecrew so we can position our modules as standards compliant

v0.36.1

🤖 Automatic Updates

Update context.tf @cloudpossebot (#165)

what

This is an auto-generated PR that updates the context.tf file to the latest version from cloudposse/terraform-null-label

why

To support all the features of the context interface.