v0.13.0

enable sns topic encryption @kevcube (#39)

what

• can now enable encryption on the sns topic

why

• we're encrypting everything

references

N/A

v0.12.7

🚀 Enhancements

IAM role fails to create without SNS topic @kevcube (#40)

what

• The IAM role for putting objects into S3 can only be created if create_sns_topic is true, because the data object on line 144 depends on it, and the IAM role currently needs this data object

why

• I was unable to instantiate this module with both create_sns_topic = false and create_iam_role = true

references

• main.tf lines 99, 145

v0.12.6

🤖 Automatic Updates

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

This PR contains the following updates:

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

---

Release Notes

cloudposse/terraform-aws-iam-role

v0.13.0

Compare Source

Add permissions_boundary as a variable @​mmorejon (#​30)

#### what * Add `permissions_boundary` as a parameter #### why * This parameter is missing in the module as an option. #### references * [iam_role#permissions_boundary](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/iam_role#permissions_boundary)

Signed-off-by: Manuel Morejon [email protected]

v0.12.0

Compare Source

update assume actions variable to support multiple actions @​mcalhoun (#​29)

#### what

• Rename the assume_role_action variable to assume_role_actions
• Update the assume_role_action to allow multiple actions
• Update the default action to include sts:TagSession

why

• Allow the flexibility of adding multiple actions to the trust policy

NOTE: THIS PR CONTAINS A BACKWARD-INCOMPATIBLE CHANGE

v0.11.0

Compare Source

Add instance profile @​sebastianmacarescu (#​27)

#### what * add option to create instance profile for the role #### why * we should be able to use this module to create a role for an ec2 instance #### references * https://github.com/cloudposse/terraform-aws-iam-role/issues/26

v0.10.1

Compare Source

🤖 Automatic Updates

Update context.tf @​cloudpossebot (#​28)

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

v0.10.0

Compare Source

Remove dependency from policy-document-aggregator @​goruha (#​25)

#### what * Replace "cloudposse/terraform-aws-iam-policy-document-aggregator" with https://registry.terraform.io/providers/hashicorp/aws/latest/docs/data-sources/iam_policy_document#example-of-merging-override-documents #### why * Reduce complexity

---

Configuration

📅 Schedule: At any time (no schedule defined).

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

♻ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

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

---

• If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by WhiteSource Renovate. View repository job log here.

v0.12.5

🤖 Automatic Updates

Update Terraform cloudposse/label/null to v0.25.0 @renovate (#31)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/label/null (source)	module	minor	0.24.1 -> 0.25.0

---

Release Notes

cloudposse/terraform-null-label

v0.25.0

Compare Source

Add "tenant", "labels_as_tags", and "descriptors" @​Nuru (#​132)

##### what - Add additional label and `id` component: `tenant` - New input `labels_as_tags` controls which labels are exported as tags - New input `descriptor_formats` generates new output `descriptors` - Update README, remove link to obsolete `terraform-terraform-label` ##### why - Support users that host resources on behalf of and/or dedicated to single customers - Supersedes and closes #​131, giving people control over which tags the module generates - Simple mechanism for creating multiple identifiers from the same inputs, reducing the need to create multiple instances of `null-label` - Document `tenant`, `labels_as_tags`, `descriptor_formats`, add additional clarification, stop promoting obsolete module

Fix: Update README Snippets @​korenyoni (#​130)

##### what * Update README snippets to reflect use of Terraform Registry. ##### why * Including snippets that reflect use of the Terraform Registry make it easier for users to quickly instantiate a null_label module. * README is out of date and does not include snippets that reflect use of the Terraform Registry. ##### references * N/A

Bridgecrew compliance @​Nuru (#​125)

##### what - Resolve Bridgecrew compliance complaint about example Autoscaling Group (BC_AWS_GENERAL_31) - Fix typo in README - Include Terraform lock file in `.gitignore` ##### why - Get clean Bridgecrew badge - Correct confusing error - Ensure lock files are not checked into GitHub ##### note The PR can and should be merged into `master` to update README and Bridgecrew without triggering a new release/version. These changes have no effect on the actual module in use and a release will create unnecessary ripple effects. However, merging to `master` will update the README and badges, so is worthwhile, and the changes will move forward into the next release.

---

Configuration

📅 Schedule: At any time (no schedule defined).

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

♻ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

🔕 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 has been generated by WhiteSource Renovate. View repository job log here.

v0.12.4

🤖 Automatic Updates

Update Terraform cloudposse/utils/aws to v0.8.1 @renovate (#37)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/utils/aws (source)	module	patch	0.8.0 -> 0.8.1

---

Release Notes

cloudposse/terraform-aws-utils

v0.8.1

Compare Source

🚀 Enhancements

Chore: run `make github/init` @​korenyoni (#​13)

#### what * Run `make github/init`. #### why * Updates `context.tf` to that of `0.25.0`, which adds supports for the `tenant` label. * Updates GHA-workflow-related files to their latest distribution. * This repository has been inactive for 60 days, so `auto-context` was disabled. #### references * https://github.com/cloudposse/terraform-null-label/releases/tag/0.25.0

---

Configuration

📅 Schedule: At any time (no schedule defined).

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

♻ Rebasing: Whenever PR becomes conflicted, 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 has been generated by WhiteSource Renovate. View repository job log here.

v0.12.3

🤖 Automatic Updates

Update Terraform cloudposse/config/yaml to v0.8.1 @renovate (#35)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/config/yaml (source)	module	patch	0.8.0 -> 0.8.1

---

Release Notes

cloudposse/terraform-yaml-config

v0.8.1

Compare Source

🚀 Enhancements

Chore: update files affected by `make github/init` @​korenyoni (#​14)

#### what * Update files affected by `make github/init`. #### why * This updates important files relating to GitHub Actions: `CODEOWNERS`, workflow files, release-drafter configuration. #### references * https://github.com/cloudposse/build-harness/blob/5c5abeceb39cde6d75a2ee754947afeb880d7658/modules/github/Makefile.init

---

Configuration

📅 Schedule: At any time (no schedule defined).

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

♻ Rebasing: Whenever PR becomes conflicted, 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 has been generated by WhiteSource Renovate. View repository job log here.

v0.12.2

🤖 Automatic Updates

Update Terraform cloudposse/config/yaml to v0.8.0 @renovate (#33)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/config/yaml (source)	module	minor	0.7.0 -> 0.8.0

---

Release Notes

cloudposse/terraform-yaml-config

v0.8.0

Compare Source

what

• Update context.tf to null-label:0.25.0 in order to support tenant label.

why

• This repository does not have an auto-context workflow which updates its context.tf to that of null-label's latest release.
• The context.tf of null-label:0.25.0 is required in a stack configuration that uses the tenant label.

references

• https://github.com/cloudposse/terraform-null-label/releases/tag/0.25.0

---

Configuration

📅 Schedule: At any time (no schedule defined).

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

♻ Rebasing: Whenever PR becomes conflicted, 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 has been generated by WhiteSource Renovate. View repository job log here.

v0.12.1

🤖 Automatic Updates

Update context.tf @cloudpossebot (#32)

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.

v0.12.0

conformance-pack module fix for hardcoded name of resource @maximmi (#30)

what

• hardcoded name of resource fixed to use name from context

why

• conformance-pack module already build as unified module to apply any available AWS conformance packs, the only thing left is to set custom names

v0.11.1

🚀 Enhancements

Fix: Redundant Aggregation Authorization when Multi-Account Multi-Region Data Aggregation is Enabled @korenyoni (#29)

what

• Ensure that central region aggregation authorization is only provisioned when multi-account aggregation is disabled.
• Add inline comments explaining that the two aggregation authorizations are mutually exclusive.

why

• An additional aggregation authorization is being deployed to each region in every AWS account when AWS Config is deployed to multiple accounts when multi account aggregation is enabled via var.central_resource_collector_account.

references

• https://docs.aws.amazon.com/config/latest/developerguide/aggregate-data.html

🐛 Bug Fixes

Fix: Redundant Aggregation Authorization when Multi-Account Multi-Region Data Aggregation is Enabled @korenyoni (#29)

what

• Ensure that central region aggregation authorization is only provisioned when multi-account aggregation is disabled.
• Add inline comments explaining that the two aggregation authorizations are mutually exclusive.

why

• An additional aggregation authorization is being deployed to each region in every AWS account when AWS Config is deployed to multiple accounts when multi account aggregation is enabled via var.central_resource_collector_account.

references

• https://docs.aws.amazon.com/config/latest/developerguide/aggregate-data.html