Today, we are happy to announce that we have reinforced our Self-service infrastructure solution with support for Terragrunt and OpenTofu Iac frameworks.

ControlMonkey’s solution for self-service enables DevOps teams to allow other teams to spin up secure and compliant cloud environments on their own in minutes by using predefined Terraform templates.
Self-service Infrastructure enables agility without sacrificing governance and frees DevOps teams from responding to tickets for infrastructure provisioning.

ControlMonkey users that use Terragrunt or OpenTofu IaC frameworks can now allow other teams to launch cloud environments using our Self-service solution, which promotes engineering autonomy and increases team productivity while maintaining governance.

As supporters of the OpenTofu project, we are excited to see more of the ControlMonkey capabilities support the OpenTofu code, and we have a lot more coming your way.

Are you using OpenTofu and want to learn more about how the ControlMonkey platform can help you with your Day 2 challenges? Our team is waiting to hear from you; we promise we will blow your mind.

Today, we’re excited to announce that ControlMonkey now supports Terraform Microsoft Teams integration for real-time infrastructure notifications. With this new capability, DevOps teams can receive critical updates—such as drift detection, deployment successes or failures, and compliance guardrail alerts—directly inside their Microsoft Teams channels.

Real-time visibility is essential in modern Terraform workflows. Without instant alerts, misconfigurations or failed deployments can go unnoticed, slowing down response times and increasing operational risk. By connecting Terraform with Microsoft Teams, ControlMonkey ensures your team stays aligned, reacts faster, and collaborates on issues in the same space where they already communicate daily.

How to Use Terraform Microsoft Teams Integration in ControlMonkey

With ControlMonkey notifications, you can get notified about various important events that happen on your infrastructure directly to your team collaboration application.
Events such as ‘Drift detected’ or ‘Deployment is done/failed’ and more.

So if you’re using Microsoft Teams, you can get these event notifications directly to a Teams channel and ensure you never miss them.

What is Microsoft Teams?

Microsoft Teams is one of the most widely used collaboration platforms, trusted by millions of organizations worldwide. It brings together chat, video meetings, file sharing, and integrations with hundreds of business applications in a single workspace. For distributed engineering teams, it acts as the central hub for daily communication and decision-making.

In a DevOps environment, Microsoft Teams goes beyond messaging. It enables ChatOps workflows, where infrastructure events and alerts flow directly into team channels. Engineers can discuss issues, approve changes, and resolve incidents without leaving the collaboration space they already use. By integrating Terraform notifications into Teams, DevOps teams gain faster visibility into infrastructure changes, reducing context-switching and accelerating incident response.

Today ControlMonkey is pleased to announce that we have reinforced our Terraform Import Engine with the ability to Import AWS Direct Connect resources to Terraform.

AWS Direct Connect is a networking service that provides an alternative to using the internet to connect to AWS. Using AWS Direct Connect, data that would have previously been transported over the internet is delivered through a private network connection between private facilities and AWS.

ControlMonkey now supports one-click Terraform Import of the following Direct Connect resources:

Connections (aws_dx_connection)
Lag (aws_dx_lag)
Virtual Interface (aws_dx_private_virtual_interface)

Are you using Direct Connect and have resources that you would like to shift to Terraform?
Feel free to book an intro meeting  with us to learn more!

ControlMonkey solution for Terraform CI/CD acts as a quality gate for any changes performed to the infrastructure in the Git repository, so whenever someone pushes new code, we run a procedure called ‘Deployment’ that validates the code change and runs ‘Terraform Apply’, in case all tests pass successfully.

Today we are pleased to announce that we have enhanced our CI/CD solution with Approval Policies, an additional validation mechanism for any infrastructure change done in your Git repository.
Starting today, ControlMonkey users can set approval policies that require the review of any requested infrastructure change.
These approval policies can be applied to a namespace or to a specific stack for that extra layer of granularity.

Setting approval policies introduces a manual approval step before the ‘Terraform Apply’ command actually runs. By default, Every deployment requires manual approval.

Types of approval policies:

• Auto Approve
• Require 1 approval
• Require 2 approvals

Changes to production are always risky, but with ControlMonkey Approved Policies, you can add an extra layer of control and prevent costly misconfigurations before every ‘Terraform Apply’ is executed.

Approval Policies are predefined and are available out of the box, so no manual policy writing is needed here.
Interested to learn how ControlMonkey streamlines every infrastructure change and helps companies like yours in their Day 2?
Our team is waiting to speak with you!

Here at ControlMonkey, we strive to provide a completely customer-centric Terraform Operations platform for our users, right from the onboarding.

So today we are happy to announce a huge enhancement to the ControlMonkey platform onboarding with our new release, Terraform Repo Scanner.
This new capability automatically scans all the repos that contain the Terraform/Terragrunt/OpenTofu code and displays all the paths that are not managed by ControlMonkey, the IaC type, and the number of resources under that path, and with a single click enables the user to create “Stacks” in the ControlMonkey platform.

This is big news for new ControlMonkey customers who are onboarding their accounts because rather than manually creating “stacks” based on existing paths in the repo, they can generate all the stacks in one shot, saving them precious time.

So if you have your own Terraform Code and are looking to leverage ControlMonkey’s advanced solutions like Terraform CI/CD with proactive policies and Drift Detection & Remediation, you can now onboard in a few clicks, with absolutely zero code changes.

Onboarding ControlMonkey has never been easier, and we’re happy seeing our new customers save time starting from the onboarding.

We are proud to announce the release of our latest enhancement to ControlMonkey Terraform CI/CD solution, managed policies for security.

Our Terraform CI/CD solution enables DevOps to proactively set preventive security controls (Control Policies) on any new pull request.
Up until today, ControlMonkey users easily created custom security policies that enforced their organization’s security standards, and now with this release, these policies are available out of the box.

ControlMonkey’s managed policies for security are predefined policies, which are managed and maintained by ControlMonkey.
Rather than writing and maintaining common security policies from scratch (with OPA or any equivalent language), we are now offering proactive managed policies for security, right out of the box.

Additionally, DevOps teams can choose on which namespaces or stacks these policies will be enforced, and also the enforcement level (warning or block).
So if you need to separate and divide your policy enforcement across environments, you now have the deeper level of granularity to do so.

The advantages of the ControlMonkey Managed Policies Solution:

• You get a library of pre-defined security policies to choose from, straight out of the box.
• Save time on writing, managing, and maintaining these policies, ControlMonkey does all the heavy lifting for you.
• By shifting left your security, you are:
  • Preventing security issues before they reach production
  • Saving time on manual code review when making a change or rolling back when needed.
  • Educating the DevOps team on the organization’s security standards

This feature came as a request we got from a few of our customers, so we are glad to see this come to life.
We are proud to collaborate with our customers on designing and building the ControlMonkey platform.

ControlMonkey’s Self-service Infrastructure solution enables other teams such as Dev and QA to launch cloud environments on their own, under DevOps governance.

Today we are pleased to announce our latest upgrade to the proactive governance capabilities of our Self-service solution, Variables Conditions.

With pre-defined variable conditions, DevOps teams can prevent other teams from launching their cloud environment, in case that environment violates any condition.

For example, DevOps can set a condition that other teams can only spin up certain instance types, that way they can ensure that the cost of that infrastructure is not over budget.

We’re honored to share that AWS has granted ControlMonkey the DevOps ISV Partner Competency.

AWS DevOps Competency

AWS DevOps Competency Partners are businesses that have demonstrated expertise in delivering DevOps solutions on AWS Infrastructure.

We have been identified by AWS as a partner that offers a range of services and software products that simplify provisioning and managing infrastructure, automate software release processes, and integrate security best practices, policies, and guardrails into CI/CD pipelines.

ControlMonkey is AWS native and we are thankful for being technologically recognized by the amazing team at AWS.

With this competency, we’re looking forward to expanding our partnership to new frontiers