v0.5.0

• No changes

v0.4.8

🚀 Enhancements

Fix Security Group Outputs @milldr (#24)

what

• compact() module.mwaa_security_group.* outputs

why

• Fix edge case error:

│ Error: Invalid function argument
│
│   on .terraform-x/modules/mwaa_environment/outputs.tf line 52, in output "security_group_arn":
│   52:   value       = join("", module.mwaa_security_group.*.arn)
│     ├────────────────
│     │ module.mwaa_security_group is object with 4 attributes
│
│ Invalid value for "lists" parameter: element 0 is null; cannot concatenate null values.
╵

v0.4.7

🤖 Automatic Updates

chore(deps): update terraform cloudposse/security-group/aws to v1.0.1 @renovate (#23)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/security-group/aws (source)	module	patch	1.0.0 -> 1.0.1

---

v0.4.6

🤖 Automatic Updates

chore(deps): update terraform cloudposse/security-group/aws to v1 @renovate (#22)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/security-group/aws (source)	module	major	0.4.3 -> 1.0.0

---

v0.4.5

🤖 Automatic Updates

chore(deps): update terraform cloudposse/s3-bucket/aws to v2.0.1 @renovate (#21)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/s3-bucket/aws (source)	module	patch	2.0.0 -> 2.0.1

---

Release Notes

cloudposse/terraform-aws-s3-bucket

v2.0.1

Compare Source

git.io->cloudposse.tools update @​dylanbannon (#​149)

#### what and why Change all references to `git.io/build-harness` into `cloudposse.tools/build-harness`, since `git.io` redirects will stop working on April 29th, 2022. #### References - DEV-143

#### 🚀 Enhancements

Use object lock enabled @​nitrocode (#​148)

#### what * Use object lock enabled #### why * Deprecation of dynamic `object_lock_configuration` for `object_lock_enabled`

│ Warning: Argument is deprecated
│
│   with module.bucket.aws_s3_bucket.default,
│   on .terraform/modules/bucket/main.tf line 30, in resource "aws_s3_bucket" "default":
│   30: resource "aws_s3_bucket" "default" {
│
│ Use the top-level parameter object_lock_enabled and the aws_s3_bucket_object_lock_configuration resource instead

references

• https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3\_bucket#object_lock_enabled
• Previous PR https://github.com/cloudposse/terraform-aws-s3-bucket/pull/144 (this did not use object_lock_enabled and only removed the dynamic)

---

v0.4.4

🤖 Automatic Updates

chore(deps): update terraform cloudposse/iam-role/aws to v0.16.2 @renovate (#19)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/iam-role/aws (source)	module	patch	0.16.1 -> 0.16.2

---

Release Notes

cloudposse/terraform-aws-iam-role

v0.16.2

Compare Source

🚀 Enhancements

Add enabled check to data source @​nitrocode (#​45)

##### what * [x] Add enabled check to data source * [x] Add TestExamplesCompleteDisabled check ##### why * Prevent creation if enabled is false ##### references * https://github.com/cloudposse/terraform-aws-s3-bucket/pull/148

---

v0.4.3

🤖 Automatic Updates

Update Terraform cloudposse/s3-bucket/aws to v2 @renovate (#17)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/s3-bucket/aws (source)	module	major	0.49.0 -> 2.0.0

---

Release Notes

cloudposse/terraform-aws-s3-bucket

v2.0.0

Compare Source

Version 2.0 of terraform-aws-s3-bucket is the same as v0.49.0 except for the addition of 2 small bug fixes (see #​147). It is labeled v2.0 as part of Cloud Posse's transition to production Semantic Versioning conventions, and to indicate significant changes as compared to v1.0 (essentially version 0.47.1). Additional upgrade information is in the repo Wiki

Breaking change:

• The website_inputs are broken (see #​141). When we get them fixed, we will likely deprecate the variable in favor of new variables that include new features available in the provider. If you are using website_inputs, do not upgrade to v2.x until #​141 is closed.

Additional notes

There are some quirks to be aware of:

• NO ACTION IS NEEDED to upgrade directly from v0.49.0 to v2.0.0
• Version 1.0 derives from and is compatible with version 0.47.1. Follow the upgrade instructions if upgrading from one of these versions.
• Version 0.48.0 was an interim release that is not recommended for anyone to use. It has incompatibilities with every other version. If you are on v0.48.0, you can upgrade directly to v2.0.0 and if Terraform gives you no complaints, then you are good to go. See the release notes for v0.48.0 and v0.49.0 for information about how to fix any breakage.

Bug fixes @​Nuru (#​147)

#### what && why - Require AWS provider v4.9.0 or later, resolves #​137 - Properly consider `source_policy_documents` input, fixes #​145

v1.0.0

Compare Source

Version 1.0.0 is part of Cloud Posse's conversion to production Semantic Versioning, part of Cloud Posse's general policy to convert to production versioning as we make updates to relatively mature modules, especially those where we see breaking changes coming in the near future. In the case of this module, the breaking changes have already been released as v2.0.0. This is a quirk due to not previously using production Semantic Versioning.

TAKE NOTE:

• Despite the 1.0 version designation, it is actually not compatible with the latest previous release (v0.49.0) or the current recommended release (v2.0.0). Because of that, this version is only recommended for people currently using v0.47.1 or earlier.
• This release is the same as v0.47.1 except for additional version pinning allowing it to work with AWS provider v4.
• No maintenance is planned for v1. With the release of AWS provider v4.9.0, the upgrade to v2.0 of this module requires no manual intervention as long as you meet the prerequisites (AWS provider v4.9.0 or later, Terraform v1.0.0 or later). So we recommend upgrading to v2.0 to get any bug fixes or new features.

---

v0.4.2

🤖 Automatic Updates

Update Terraform cloudposse/iam-role/aws to v0.16.1 @renovate (#15)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/iam-role/aws (source)	module	patch	0.16.0 -> 0.16.1

---

Release Notes

cloudposse/terraform-aws-iam-role

v0.16.1

Compare Source

🚀 Enhancements

Disabling all tags in all iam resources @​jamengual (#​44)

#### what * In https://github.com/cloudposse/terraform-aws-iam-role/pull/43 I added the option to disable role tags but in environments where roles are created under very strict controls, the policy tags for the roles sometimes can't be tagged. This change disable tags for all IAM related resources. * #### why * to disable tags for role-related things. Use one variable instead of two. #### references * https://github.com/cloudposse/terraform-aws-iam-role/pull/43

---

v0.4.1

🤖 Automatic Updates

Update Terraform cloudposse/iam-role/aws to v0.16.0 @renovate (#14)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/iam-role/aws (source)	module	minor	0.15.0 -> 0.16.0

---

Release Notes

cloudposse/terraform-aws-iam-role

v0.16.0

Compare Source

Making tags for roles optional @​jamengual (#​43)

#### what * Make role tags optional * #### why * Restrictive policy boundaries do not allow tag roles in highly secure environments.

---

v0.4.0

fix: Change kms policy statement resource to NOT resource @devops-chris (#11)

what

• Changed IAM execution role Policy KMS permission statement from a resource to a NotResource

why

• This change complies with the suggested policy for an AWS owned key.
• Experienced that task logs were not generated in Cloudwatch and DAGs fail in Airflow with an error such as: 'Could not read remote logs from log_group: XXXXXXX'

references

• AWS Recommended Policy for AWS owned key: https://docs.aws.amazon.com/mwaa/latest/userguide/mwaa-create-role.html#mwaa-create-role-aocmk