Read our newest book, Fundamentals of DevOps and Software Delivery, for free!

Gruntwork Newsletter, December, 2023

Headshot of Yevgeniy Brikman

Yevgeniy Brikman

DEC 21, 2023 | 7 min read
Featured Image of Gruntwork Newsletter, December, 2023
Every few months, we send out a newsletter to all Gruntwork customers that describes all the updates we’ve made since the last newsletter and news from the DevOps industry. Note that many of the links below go to private repos in the Gruntwork Infrastructure as Code Library and Reference Architecture that are only accessible to customers.Hello Grunts,In the last few months, we updated our Landing Zone solution with a self-service account factory that can automate the process of setting up a new multi-account structure and full SDLC (Software Development Life Cycle) workflow for your dev teams; updated our VPC code with support for IPv6, IPAM, transit subnets, private NATs, and black hole routes; and made huge progress on OpenTofu, including a release candidate that may become our first stable release. Also, one more reminder: Gruntwork will be closed for two weeks for the winter break. Happy holidays!As always, if you have any questions or need help, email us at!

Gruntwork’s Landing Zone solution now supports a self-service account factory that can automate the process of setting up a new multi-account structure and full SDLC (Software Development Life Cycle) workflow for your dev teams. Here’s a quick outline of how it works:
  • 1.Fill out the account request form. Your dev team fills out a web form (which you can customize to your needs), specifying the details of the account structure they need: e.g., team name, department, billing code, etc.
  • 2.Automated account creation in Control Tower. When they submit the form, this kicks off an automated account provisioning process that provisions new AWS accounts for that team—e.g., dev, stage, and prod—using Control Tower. This allows you to use Control Tower as your single pane of glass for all of your AWS accounts.
  • 3.Automated baselining. The automated account provisioning process applies a secure baseline to every account, ensuring it is configured with CloudTrail, GuardDuty, Macie, IAM Access Analyzer, default EBS encryption, Security Hub, IAM roles, SSO access, OIDC providers, and all the other security, monitoring, and auth features you need.
  • 4.Automated networking. The automated account provisioning process configures networking in the new AWS account, including setting up a VPC, subnets, routes, Internet gateways, NAT gateways, and Transit Gateway (TGW) associations and routing.
  • 5.Automated repo scaffolding. The automated account provisioning process creates a new GitHub repo for the team that is pre-configured with Terraform and Terragrunt best-practices out of the box, including the recommended multi-account folder structure, backend configuration, automated testing practices, and more.
  • 6.Automated CI / CD. The automated account provisioning process sets up Gruntwork Pipelines inside the new GitHub repo, configuring a GitOps-driven CI / CD workflow that automatically runs plan and apply, automated tests, policy checks, and enforces ACLs on every commit and pull request.
  • 7.Automated updates and promotion workflows. The automated account provisioning process sets up Patcher inside the new GitHub repo so that all dependencies are updated automatically via pull requests. These pull requests promote new versions of your dependencies to one environment at a time: e.g., Patcher will first automatically open a PR in dev to update you to the new version; once that is merged and deployed, Patcher will automatically open a PR in stage; and finally, once that is merged and deployed, Patcher will automatically open a PR in prod.
To learn more, read the DevOps Foundations blog post. If you’re interested in a demo or getting access, please reach out to our sales team!

We’ve made a number of updates to our VPC modules, including adding support for:
  • IPv6 support.
  • Auto provisioning CIDR blocks from AWS IPAM.
  • An optional fourth tier of subnets called “transit subnets”, which are useful for connecting to Transit Gateways.
  • Deploying NATs into private subnets rather than public, which is also useful in conjunction with Transit Gateways.
  • “Black hole” routes (using an ENI not connected to anything).
  • A way to look up VPC data when the VPC code is managed in another repo (so you can’t use dependency blocks or terraform_remote_state).
Check out the vpc-app module, vpc service, and vpc-app-lookup module for the details!

A small holidays gift for everyone: the OpenTofu release candidate is now available! If we find no major issues, this release candidate will become our first stable release on January 10th, 2024!This is a huge milestone. In 4 months, we’ve gone from the OpenTofu manifesto to 1000+ PRs & issues, 60+ contributors, 50K+ stars (manifesto + OpenTofu), a brand new registry, alpha release, beta release, and now, a release candidate. Read the announcement blog post for the full details.Give the OpenTofu release candidate a shot—it should be a drop-in replacement for Terraform—and let us know how it works for you. Installation instructions are here and can be as easy as brew install opentofu.

As we do every year, the Gruntwork team will be taking some time off for the winter break. We will be officially closed December 25th — January 5th. We will not be handling support tickets or Slack inquiries during this time, so please plan accordingly.Thank you for being a Gruntwork customer. We are deeply grateful that you’ve chosen to work with us, helping us make world-class infrastructure and DevOps practices accessible to everyone. We have some very exciting things planned for 2024 and can’t wait to share them with you!

You can find details on every single release and update we do in the Gruntwork Releases page of our docs site. And now, you can use Patcher to update your dependencies automatically! If you’re a Gruntwork customer and don’t have access to Patcher yet, please email If you’re not a Gruntwork customer, please contact our sales team.Here are the dedicated pages for new Gruntwork releases since the last newsletter:

AWS has announced Aurora Limitless:

Scale your Amazon Aurora clusters to millions of write transactions per second and manage petabytes of data. With this new capability, you can scale your relational database workloads on Aurora beyond the limits of a single Aurora writer instance without needing to create custom application logic or manage multiple databases.

Testimonial Profile Image

Testimonial Profile Image
If you’d be interested in support for this in our RDS modules, please file an enhancement request issue in the terraform-aws-data-storage repo.

AWS has made two improvements to authn and authz for EKS:
  • 1.Simplified EKS cluster access. In the past, to control access to an EKS cluster, AWS required you to use a ConfigMap to map between IAM roles and EKS permissions, which was always a clunky and awkward experience. AWS has now launched a simpler way to manage access to your EKS clusters.
  • 2.Simplified Pod IAM role access. AWS has also a feature called EKS Pod Identity which makes it easier to grant your EKS Pods access to IAM roles.
We will be looking to add support for both of these features in our EKS modules soon.

AWS has announced that Lambda functions will now scale up to 12x faster:

With this improvement each function can scale up to a rate of 1,000 concurrent executions every 10 seconds, up to your account concurrency limit.

Testimonial Profile Image

Testimonial Profile Image
The new scaling experience is already live and enabled by default for all functions.Amazon has announced zero-ETL integrations with Amazon Redshift and/or OpenSearch for several of their data stores:

Explore our latest blog

Get the most up-to-date information and trends from our DevOps community.
TerraformResouces Image

Promotion Workflows with Terraform

How to configure GitOps-driven, immutable infrastructure workflows for Terraform using Gruntwork Patcher.

Jason Griffin

October 3, 2023 7 min read
TerraformResouces Image

The Impact of the HashiCorp License Change on Gruntwork Customers

How to configure GitOps-driven, immutable infrastructure workflows for Terraform using Gruntwork Patcher.

Josh Padnick

October 3, 2023 7 min read