Skip to content

v1.536.1

Choose a tag to compare

View all tags
@cloudposse-releaser cloudposse-releaser released this 19 May 21:24
· 33 commits to refs/heads/main since this release
v1.536.1
3c13a84
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
Add new output `account_name_id_map` @Benbentwo (#19) ## what * another output

why

  • Provides a map of account_name to id for all accounts including organization owner.

Summary by CodeRabbit

  • New Features
    • Added a new output that provides a map of account names to their account IDs, including the root account.

🤖 Automatic Updates

chore(deps): update terraform cloudposse/service-control-policies/aws to v0.15.1 @[renovate[bot]](https://github.com/apps/renovate) (#3) This PR contains the following updates:
Package Type Update Change
cloudposse/service-control-policies/aws (source) module minor 0.9.2 -> 0.15.1

Release Notes

cloudposse/terraform-aws-service-control-policies (cloudposse/service-control-policies/aws)

v0.15.1

Compare Source

🚀 Enhancements
Update EC2 policies to include new instance types @​Nuru (#​64)
what
  • Update DenyEC2NonNitroInstances and DenyEC2InstancesWithoutEncryptionInTransit to include instances made available since the last update
why
  • Allow qualifying instances that would have otherwise been denied because they were too new

v0.15.0

Compare Source

feat: Add require ebs encryption scp @​wavemoran (#​60)
what
  • Adds SCP to require EBS volume encryption
why
  • Encrypting EBS volumes is a good default security policy
  • Seems like a common enough policy to include in the provided catalog
references
Run tests 1 policy at a time @​goruha (#​62)
what
  • Run tests 1 policy at a time
why
  • Workaround service control policies limits
🚀 Enhancements
chore(deps): bump github.com/hashicorp/go-getter from 1.7.3 to 1.7.5 in /test/src in the go_modules group @​dependabot (#​57) Bumps the go_modules group in /test/src with 1 update: [github.com/hashicorp/go-getter](https://redirect.github.com/hashicorp/go-getter).

Updates github.com/hashicorp/go-getter from 1.7.3 to 1.7.5

Release notes

Sourced from github.com/hashicorp/go-getter's releases.

v1.7.5

What's Changed

New Contributors

Full Changelog: https://github.com/hashicorp/go-getter/compare/v1.7.4...v1.7.5

v1.7.4

What's Changed

Full Changelog: https://github.com/hashicorp/go-getter/compare/v1.7.3...v1.7.4

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
    You can disable automated security fix PRs for this repo from the Security Alerts page.
🤖 Automatic Updates
chore(deps): bump github.com/hashicorp/go-getter from 1.7.3 to 1.7.5 in /test/src in the go_modules group @​dependabot (#​57) Bumps the go_modules group in /test/src with 1 update: [github.com/hashicorp/go-getter](https://redirect.github.com/hashicorp/go-getter).

Updates github.com/hashicorp/go-getter from 1.7.3 to 1.7.5

Release notes

Sourced from github.com/hashicorp/go-getter's releases.

v1.7.5

What's Changed

New Contributors

Full Changelog: https://github.com/hashicorp/go-getter/compare/v1.7.4...v1.7.5

v1.7.4

What's Changed

Full Changelog: https://github.com/hashicorp/go-getter/compare/v1.7.3...v1.7.4

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
    You can disable automated security fix PRs for this repo from the Security Alerts page.
Migrate new test account @​osterman (#​59)
what
  • Update .github/settings.yml
  • Update .github/chatops.yml files
why
  • Re-apply .github/settings.yml from org level to get terratest environment
  • Migrate to new test account
References
  • DEV-388 Automate clean up of test account in new organization
  • DEV-387 Update terratest to work on a shared workflow instead of a dispatch action
  • DEV-386 Update terratest to use new testing account with GitHub OIDC
Update .github/settings.yml @​osterman (#​58)
what
  • Update .github/settings.yml
  • Drop .github/auto-release.yml files
why
  • Re-apply .github/settings.yml from org level
  • Use organization level auto-release settings
references
  • DEV-1242 Add protected tags with Repository Rulesets on GitHub
Update release workflow to allow pull-requests: write @​osterman (#​56)
what
  • Update workflow (.github/workflows/release.yaml) to have permission to comment on PR
why
  • So we can support commenting on PRs with a link to the release
Update GitHub Workflows to use shared workflows from '.github' repo @​osterman (#​54)
what
  • Update workflows (.github/workflows) to use shared workflows from .github repo
why
  • Reduce nested levels of reusable workflows
Update GitHub Workflows to Fix ReviewDog TFLint Action @​osterman (#​53)
what
  • Update workflows (.github/workflows) to add issue: write permission needed by ReviewDog tflint action
why
  • The ReviewDog action will comment with line-level suggestions based on linting failures
Update GitHub workflows @​osterman (#​52)
what
  • Update workflows (.github/workflows/settings.yaml)
why
  • Support new readme generation workflow.
  • Generate banners

v0.14.2

Compare Source

🐛 Bug Fixes
Minor cleanups @​Nuru (#​50)
what

Minor fixes to several SCPs

  • DenyLambdaWithoutVpc was previously invalid. It is now valid, but has not been thoroughly tested to ensure it does what it promises.
  • DenyRDSUnencrypted was fixed to deny rds:RestoreDBClusterFromSnapshot when not encrypted. Previously this action was not denied, and instead the nonexistent RestoreDBClusterFromDBSnapshot was denied
  • The DenyS3BucketsPublicAccess policy was cleaned up by eliminating the nonexistent s3:DeletePublicAccessBlock action. Note that it still is probably not something you want to use, because it denies enabling a public access block as well as removing one. We hope to have a better policy in the future.
  • The Region Restriction Templates DenyRegions and RestrictToSpecifiedRegions were updated to exclude the account, artifact, and supportplans services from region restrictions, since they are global services. The obsolete awsbillingconsole service was removed.
  • DenyS3InNonSelectedRegion was fixed to allow users to allow S3 bucket creation in us-east-1. Previously us-east-1 was always prohibited even when expressly allowed, due to quirks in S3.
why
  • Restore intended behavior
references

v0.14.1: Fix encryption-in-transit requirements

Compare Source

[!warning]
When the DenyEC2NonNitroInstances policy was first introduced, it was primarily intended
to ensure that network traffic was encrypted in transit, which was seen to be a feature
that all Nitro instances supported and all non-Nitro instances did not. However, this
is not the case, as instance families such as a1, t3, and t4g are Nitro based but
do not support network traffic encryption in transit.

As such, the DenyEC2NonNitroInstances policy is not a reliable way to ensure that
network traffic is encrypted in transit. It is recommended that you use the
DenyEC2InstancesWithoutEncryptionInTransit policy instead if that is your goal.

[!caution]
These changes could have the side effect of having other policies that were previously configured but ignored to start being enforced. The previous version of these updated policies were too big and thus any policy that included them was not enforced. It is possible that upgrading to this version will cause not just this policy to be updated, but cause other policies (statements) that were previously not enforced due to the overall size of the SCP to become enforced now that the full SCP is valid.

🐛 Bug Fixes
Update/Fix EC2 Policies @​Nuru (#​49)
what
  • Update/fix EC2 Policies DenyEC2InstancesWithoutEncryptionInTransit and DenyEC2NonNitroInstances
  • Update test framework (even though testing does not work)
why
  • Prior policies exceeded 5120-character length limit and were also out of date
  • Satisfy Dependabot
references
🤖 Automatic Updates
Use GitHub Action Workflows from `cloudposse/.github` Repo @​osterman (#​47)
what
  • Install latest GitHub Action Workflows
why
  • Use shared workflows from cldouposse/.github repository
  • Simplify management of workflows from centralized hub of configuration
Add GitHub Settings @​osterman (#​42)
what
  • Install a repository config (.github/settings.yaml)
why
  • Programmatically manage GitHub repo settings
Update Scaffolding @​osterman (#​40)
what
  • Reran make readme to rebuild README.md from README.yaml
  • Migrate to square badges
  • Add scaffolding for repo settings and Mergify
why
  • Upstream template changed in the .github repo
  • Work better with repository rulesets
  • Modernize look & feel
Update Scaffolding @​osterman (#​39)
what
  • Reran make readme to rebuild README.md from README.yaml
  • Migrate to square badges
  • Add scaffolding for repo settings and Mergify
why
  • Upstream template changed in the .github repo
  • Work better with repository rulesets
  • Modernize look & feel
Update Scaffolding @​osterman (#​38)
what
  • Reran make readme to rebuild README.md from README.yaml
  • Migrate to square badges
  • Add scaffolding for repo settings and Mergify
why
  • Upstream template changed in the .github repo
  • Work better with repository rulesets
  • Modernize look & feel
Update Scaffolding @​osterman (#​37)
what
  • Reran make readme to rebuild README.md from README.yaml
  • Migrate to square badges
  • Add scaffolding for repo settings and Mergify
why
  • Upstream template changed in the .github repo
  • Work better with repository rulesets
  • Modernize look & feel
Update Scaffolding @​osterman (#​36)
what
  • Reran make readme to rebuild README.md from README.yaml
  • Migrate to square badges
  • Add scaffolding for repo settings and Mergify
why
  • Upstream template changed in the .github repo
  • Work better with repository rulesets
  • Modernize look & feel
Update Scaffolding @​osterman (#​35)
what
  • Reran make readme to rebuild README.md from README.yaml
  • Migrate to square badges
  • Add scaffolding for repo settings and Mergify
why
  • Upstream template changed in the .github repo
  • Work better with repository rulesets
  • Modernize look & feel

v0.14.0

Compare Source

Ensure support of the AWS Provider V5 and latest terraform @​max-lobur (#​31)
what

Ensure support of the AWS Provider V5
Update terraform version
Update dependencies in tests
Linter fixes

why

Maintenance

references

https://github.com/hashicorp/terraform-provider-aws/releases/tag/v5.0.0

update AWS family policies for mid-2023 @​jonathan-3play (#​30)
what
  • Updated to all EC2 families as of 2023-06-23 that AWS documentation indicate are Nitro-based or support inherent encryption in transit.
why
  • Discovered that many useful EC2 families that should be permitted were in fact blocked.
references
Sync github @​max-lobur (#​25)

Rebuild github dir from the template

v0.13.0

Compare Source

  • No changes

v0.12.0

Compare Source

Update DenyEC2InstancesWithoutEncryptionInTransit @​Nuru (#​23)
what
  • Update DenyEC2InstancesWithoutEncryptionInTransit policy with current list of instances
  • Move policies requiring template parameters to separate sub-directories
  • Fix DenyS3InNonSelectedRegion policy
  • Replace DenyRegionUsage policy with DenyRegions and RestrictToSpecifiedRegions policies
why
  • Previous policy was missing a lot of instance types that provide encryption in transit, such as c6i, c7g, and g5 to name a few
  • Allow people to include catalog/*.yaml without needing to specify any parameters
  • The DenyS3InNonSelectedRegion policy was completely broken, having no effect
  • The DenyRegionUsage policy was confusing, because it took a parameter called regions_lockdown which was a list of regions to allow. The new policies let you choose to either whitelist or blacklist regions.
references
  • Supersedes and closes #​22
git.io->cloudposse.tools update @​dylanbannon (#​20)
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

v0.11.0

Compare Source

Adding policies @​jamengual (#​11)
what
  • Adding Aditional SCPs to the catalog
  • Adding Parameters
  • Updating example
why
  • Adding AWS recommended SCPs plus some additional SCPs to improve security compliance
references

v0.10.0

Compare Source

add deny disabling cloutrail scp @​sgtoj (#​19)
what
  • add new scp to prevent cloudtrail from being disabled
why
  • prevent cloudtrail from being disabled by bad actors
references
  • n/a

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 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 was generated by Mend Renovate. View the repository job log.

Update README.md and docs @[cloudposse-releaser[bot]](https://github.com/apps/cloudposse-releaser) (#17) ## 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

Contributors

Benbentwo
Assets 2
Loading