v0.36.0

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

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.35.2

🤖 Automatic Updates

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

This PR contains the following updates:

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

---

Release Notes

cloudposse/terraform-aws-route53-cluster-hostname

v0.10.1

Compare Source

🤖 Automatic Updates

Update README.md and docs @​cloudpossebot (#​33)

#### what This is an auto-generated PR that updates the README.md and docs #### why To have most recent changes of README.md and doc from origin templates

v0.35.1

🤖 Automatic Updates

Update README.md and docs @cloudpossebot (#160)

what

This is an auto-generated PR that updates the README.md and docs

why

To have most recent changes of README.md and doc from origin templates

v0.35.0

mfa_delete removed @maximmi (#159)

what

• mfa_delete removed
• Bridgecrew check Ensure S3 bucket has MFA delete enabled skipped

why

• Because terraform doesn't support this argument to be toggled (hashicorp/terraform-provider-aws#629).
• To satisfy Bridgecrew compliance scan

references

• hashicorp/terraform-provider-aws#629

v0.34.0

readme updated, BridgeCrew compliance checks fixed, code cleaned @maximmi (#158)

what

• BridgeCrew compliance checks fix
• readme updated
• default behaviour changed: S3 bucket MFA delete enabled by default
• default behaviour changed: S3 Bucket Versioning enabled by default
• default behaviour changed: Encryption of the S3 bucket enabled by default

why

• To be able to position our modules as standards compliant
• stay in sync with code
• To comply BridgeCrew check

references

• https://docs.bridgecrew.io/docs/s3_16-enable-versioning
• https://docs.bridgecrew.io/docs/s3_13-enable-logging
• https://docs.bridgecrew.io/docs/s3_14-data-encrypted-at-rest

v0.33.0

Terraform 0.14 upgrade @maximmi (#156)

what

• Upgrade to support Terraform 0.14 and bring up to current Cloud Posse standard

why

• Support Terraform 0.14

v0.32.1

🤖 Automatic Updates

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

This PR contains the following updates:

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

---

Release Notes

cloudposse/terraform-aws-route53-cluster-hostname

v0.10.0

Compare Source

Terraform 0.14 upgrade @​maximmi (#​32)

#### what - Upgrade to support Terraform 0.14 and bring up to current Cloud Posse standard #### why - Support Terraform 0.14

v0.32.0

Terraform 0.14 upgrade @maximmi (#153)

what

• Upgrade to support Terraform 0.14 and bring up to current Cloud Posse standard

why

• Support Terraform 0.14

v0.31.0

Allow to restrict S3 access @anton-kachurin (#143)

what

Adds two variables extended_ec2_policy_document and prefer_legacy_ssm_policy to be able to control IAM policies attached to EC2 instance roles.

why

As noted in #75, currently EC2 instances are configured with a role that gives full S3 access. This is undesirable for security reasons.

• AmazonEC2RoleforSSM is a managed policy allowing to use SSM features (Session Manager, for example) with EC2 instances and it gives full S3 access.
• There is an inline policy containing a statement with SID AllowS3OperationsOnElasticBeanstalkBuckets that also grants full S3 access.

The prefer_legacy_ssm_policy variable (when set to false) will replace AmazonEC2RoleforSSM with AmazonSSMManagedInstanceCore which is recommended by AWS: https://docs.aws.amazon.com/systems-manager/latest/userguide/setup-instance-profile.html
By default, it's set to true for backward compatibility.

The extended_ec2_policy_document variable takes in a JSON that may be used to override existing policy statements as long as a statement has an SID. See examples/complete/main.tf for example usage.

references

closes #75

v0.30.0

Add missing resource attributes to Spot. @razorsedge (#131)

what

• Four settings relating to EC2 Spot prices (added in #115) were missing an empty resource attribute. This causes terraform apply to constantly reapply the configuration, even if no code or Beanstalk config has changed.

why

• As #43 shows, terraform 0.12.x shows settings changes during terraform plan when no changes were done.

references

• Broken by #115.
• Applies to #43.