chore(deps): update terraform cloudposse/efs/aws to v1

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/efs/aws (source)	module	major	0.36.0 -> 1.1.0

---

Release Notes

cloudposse/terraform-aws-efs (cloudposse/efs/aws)

v1.1.0

Compare Source

Make allow_all_egress a variable @​dlacosteGFM (#​126)

What changes in this PR?

• Default change is nothing (with this PR applied, nobody would have to change anything)
• Makes a new parameter allow_all_egress which defaults to false
• When creating the security group for the EFS volume, this line makes the security-group have an "allow egress to 0.0.0.0/0" rule entry. This PR makes that a configurable parameter instead

Why make this change?

• EFS doesn't actually do egress, so this really makes no impact difference at all
• ...but during a security audit we have a dangling "why do you allow egress to 0.0.0.0/0 on this?" question with no really good answer (so let's get rid of it as it doesn't do anything anyways)

References

• PCI DSS 3.2.1 rule 1.1.7 - Requirement to review firewall and router rule sets every 6 months
• PCI DSS 3.2.1 rule 1.2.1 - Restrict inbound and outbound traffic to that which is necessary for the environment

v1.0.0

Compare Source

🤖 Automatic Updates

chore(deps): update terraform cloudposse/security-group/aws to v2 (main) @​renovate (#​135)

This PR contains the following updates:

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

---

Release Notes

cloudposse/terraform-aws-security-group (cloudposse/security-group/aws)

v2.2.0

Compare Source

`.editorconfig` Typo @​&#​8203;milldr (#&#​8203;50)

what

fixed intent typo

why

should be spelled "indent"

references

https://cloudposse.slack.com/archives/C01EY65H1PA/p1685638634845009

Sync github @​&#​8203;max-lobur (#&#​8203;47)

Rebuild github dir from the template

v2.1.0

Compare Source

• No changes

v2.0.1

Compare Source

🐛 Bug Fixes

Properly handle enabled = false @​&#​8203;Nuru (#&#​8203;45)

what

• Properly handle enabled = false

why

• Fixes #​43

v2.0.0: Breaking changes

Compare Source

For details about migrating from v1 to v2, read the migration documentation.

Version 1 of this module had a flaw in that it tried to create new security group rules before deleting the old ones, which the Terraform provider does not handle properly and caused most attempted changes to fail. Version 2 resolves this issue by also creating a new security group when the rules change, installing the new rules in the new security group, then changing the security group assignments. Read the README and the migration documentation for more details.

Document migration from v1 to v2 @​&#​8203;Nuru (#&#​8203;42)

what

• Document migration from v1 to v2 of this module
• Fix #​40

why

• Serious issues exist in v1, causing v2 to have different defaults and new settings. Documentation is needed to guide users on how to upgrade while minimizing service interruptions.

references

• Closes #​40

Fixes the link for examples/complete/main.tf @​&#​8203;jdmedeiros (#&#​8203;41)

Fixes the link for examples/complete/main.tf on the README.md file.

---

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

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

♻ Rebasing: Whenever PR is behind base branch, 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 Mend Renovate. View repository job log here.

[hans-d]

/terratest

[mergify]

/terratest

[kevcube]

/terratest