Recently, our engineering team has been developing various GCP capabilities to enhance multi-cloud support for the ControlMonkey Platform. With comprehensive releases such as Inventory Dashboard and GCP IaC Coverage, our GCP users can now leverage more advanced Terraform Automation solutions to govern and automate their GCP environments.  Today we are happy to announce the General Availability of ControlMonkey’s Terraform Import Engine for GCP Users! GCP Terraform Import!

New GCP Terraform Import

Starting today, ControlMonkey users with old systems can easily move their GCP resources to Terraform. Our AI-powered Terraform Code Generator makes this simple.
ControlMonkey’s Terraform Import Engine finds GCP resources that Terraform does not manage. It creates code that shows the resources’ current state with just one click.
Our platform also generates the Terraform state file, so you don’t need to run any ‘Import’ commands or use any ‘Import’ blocks within your code and then run ‘Apply.’

We use our Smart Stacking algorithm to find related resources. It can also create stacks that are ready to import.

Importing 1000s of GCP resources to Terraform has never been easier:

• Visualize how many resources are not managed with Terraform and their cost with the option to filter by region.

• Select the stacks to import to Terraform and choose the import method. You can also search and filter by resource type.

• Get a 100% verified Terraform code and state file that matches your resource’s configuration.

TL,DR – Terraform Import and ControlMonkey

The benefits of leveraging ControlMonkey’s Terraform Import Engine:

1. Generate Terraform code in 75% less time.
2. Increase Terraform coverage to 99%.
3. Out-of-the-box automatic custom Terraform Module creation.
4. Save thousands of DevOps hours by eliminating manual Terraform code writing.

Do you have GCP infrastructure that you’re looking to shift to Terraform? ControlMonkey offers the easiest and most swift way to do it.

Are you interested in learning more and seeing it for yourself? 
Book a 30-minute technical discussion with our Terraform Experts.

Today, we are pleased to announce another milestone in our support for Azure with the release of our Custom Terraform Modules Creation Wizard.

Following the major announcement of our Terraform Import Engine for Azure, our Azure users can now build custom Terraform modules with just a few clicks.
This enhancement makes our Terraform Import Engine a 360 automated solution that simplifies the import of Azure resources to Terraform.

Rather than spending time manually writing Custom Terraform Modules, the ControlMonkey Terraform Import Dashboard provides the easiest way to create modules with a user-friendly wizard in a few clicks.

After selecting which resources to bundle together, ControlMonkey automatically generates the Terraform module code. It’s as easy as that.

After the code is generated, users can rename the resources and extract variables to customize it even further.  

ControlMonkey saves cloud engineers precious time and improves productivity: 

• Automatically generates the Terraform module code rather than manually.
• Determines the relationship between the resources by leveraging ControlMonkey’s
  ‘Smart Stacking’ technology.
• Replicates resources or environments in a fast and productive way. 

Do you have Azure infrastructure that you’re looking to manage with Terraform?
ControlMonkey offers the easiest and most swift way to do it.

Are you interested in learning more and seeing it for yourself?
Book a 30-minute technical discussion with our Terraform Experts.

Last month, we announced the release of the Cloud Inventory Dashboard for GCP, the first significant capability of our cloud visibility solution for GCP.
We’re happy to announce another milestone in our multi-cloud support with ControlMonkey’s IaC Coverage for GCP.

Starting today, ControlMonkey customers with GCP environments can gain complete visibility into their GCP Projects and understand the following:

1. What is their IaC coverage across projects
2. What is the IaC coverage per region
3. How many resources are unmanaged by IaC

As well as:

1. IaC Coverage over time
2. IaC Distribution across IaC tools

With this new capability, companies running GCP workloads at scale with multiple projects in multiple regions can get a bird’s-eye view of their IaC coverage.

The release of the GCP IaC Coverage reinforces ControlMonkey’s multi-cloud capabilities and provides our customers with a centralized view across clouds, subscriptions/accounts/projects, and regions.

We are just getting started. In the coming months, we plan to release many exciting new capabilities for our GCP customers.

Are you running on GCP? Our team would love to jump on a call and show you how ControlMonkey can help.

As part of our multi-cloud vision of the ControlMonkey platform, we are happy to announce another milestone in our integration with GCP (Google Cloud Platform).

We kicked off our GCP support with Managed Security Policies for GCP a few months ago, and today, we are releasing the Cloud Inventory Dashboard for GCP.

ControlMonkey customers with GCP environments can now gain a 30K view of their projects and understand:

• Resources distribution across geo-region
• Resources distribution across services

With this new capability, companies running GCP workloads at scale with multiple projects in multiple regions can get a bird’s-eye view of their cloud resources.

The release of the GCP Cloud Inventory Dashboard reinforces ControlMonkey’s multi-cloud capabilities and provides our customers with a centralized view across clouds, subscriptions/accounts/projects, and regions.

We plan to release many exciting new capabilities for our GCP customers soon, so stay tuned!

Running on GCP or multi-cloud? Our team would love to jump on a call and show you how ControlMonkey can help.

When you reach a large scale, leveraging Terraform Modules to replicate cloud services across environments becomes more of a necessity than a “Nice to have.”
Most organizations leverage Terraform Modules that reside in a public registries like Hashicorp or OpenTofu or modules from public Git repositories. (e.g. source = git::ssh://[email protected]…).

But every now and then we’ve met customers that had the need to manage their modules in a private registry.
Main reason to do so is making sure their engineers use only pre-defined, compliant modules, and also to adequately manage versions of modules.
So today, we proudly announce the release of the ControlMonkey’s Terraform Private Modules Registry.

ControlMonkey’s Terraform Registry is a private registry for securely sharing, reusing, and version-controlling Terraform modules within your organization.
Starting today, ControlMonkey users can seamlessly leverage custom modules directly from their VCS without sharing credentials, and integrate them into ControlMonkey’s Terraform CI/CD.

Our Private Modules Registry enables cloud engineering teams to create trusted and reusable modules and enforce module versions within their organization. With ControlMonkey, private modules can now be easily accessible in your Terraform code.

Terraform Private Modules Registry applies a Management Layer to private modules that enables the following:

• Delete outdated module versions so they won’t be used.
• Mark specific modules as obsolete (before deletion)
• Display viable information on each module, such as:
  • Which variables are that module using
  • What outputs are defined for that module
  • Which resources are utilized in that Terraform Module
  • Which external Terraform Modules are being used in that module
  • Which Terraform Providers are specified in that module

When you use ControlMonkey as your private registry, you don’t need to be worried about authorization within your Terraform CI/CD pipeline, as we take care of it for you.

Are you leveraging Terraform Modules and looking for the easiest and safest way to manage them?
Our team is waiting to jump on a 30-minute technical discussion to see how ControlMonkey can help.

Today, we are happy to announce the latest enhancement to our Terraform CI/CD solution – “Stack Auto-discovery.”
This capability detects new folders and branches in your Git repositories and automatically creates stacks in the ControlMonkey platform.

ControlMonkey’s Terraform CI/CD solution helps cloud engineering teams. It offers a simple way to validate, plan, and deploy infrastructure changes. All of this comes from a central source of truth. With ControlMonkey, engineers can easily apply cloud policies. This includes tagging, security, and compliance in the infrastructure CI/CD process.
By proactively standardizing their cloud environments, they can prevent misconfigurations from reaching production.

Until today, ControlMonkey users had to create Stacks manually for new folders or paths in their Git repository. This was necessary for those Stacks to be part of the infrastructure CI/CD process.

New: Automatic Detection and Creation of Terraform Stacks

Now, with “Stack Auto-discovery,” ControlMonkey will find any new folder or path in the Git repository. It will then automatically create the Stack for it.
Any new Terraform code created will automatically be incorporated into the infrastructure CI/CD approval and testing process, ensuring that all resources align with the organization’s standard.

A classic use case is when a new DevOps engineer is onboarded and tasked with creating cloud environments. They create a new branch and a new folder. They also make a PR. ControlMonkey gives them instant feedback on the following:

• Which resources are going to be created if this PR will be merged.
• Which of the organization’s Cloud Policies have passed or failed, and what is the reason behind it.

TL;DR – Terraform Stacks and ControlMonkey 

To summarize, “Stack auto-discovery” provides an additional layer of automation to your GitOps. It makes sure that all your Terraform code is tested and checked before it goes to production. This reduces the chance of mistakes and misconfigurations.
Automating the whole process makes daily tasks easier. It also boosts the overall efficiency of the Cloud Engineering team. The new capability supports Terraform, OpenTofu, and Terragrunt.

ControlMonkey’s Terraform Automation Platform dramatically changes how engineering teams standardize and deploy their cloud infrastructure.
Our Terraform experts are ready for a technical discussion whenever you are.

In the past few months, our engineering team has been developing more and more Azure capabilities to enhance our multi-cloud support of the ControlMonkey Platform.
With exciting releases such as Resource Explorer, Managed Policies, and Azure IaC Coverage, our Azure users can now leverage advanced Terraform Automation solutions to manage and govern their Azure environments.

So, we are delighted to announce that we have released ControlMonkey’s Terraform Import Engine for Azure Users!

ControlMonkey’s Terraform Import Engine for Azure

Starting today, ControlMonkey users with legacy infrastructure can easily shift their Azure resources to Terraform with our AI-powered Terraform Code Generator.
ControlMonkey’s Terraform Import Engine automatically detects Azure resources not managed with Terraform and generates the code representing the resources’ current state with a single click.
Our platform also generates the Terraform state file, so you don’t need to run any ‘Import’ commands or use any ‘Import’ blocks within your code and then run ‘Apply.’

Using our Smart Stacking contextual algorithm, we can identify which resources are related to each other and automatically generate ready-to-import stacks.

Importing 1000s of Azure resources to Terraform has never been easier:

• Visualize how many resources are not managed with Terraform and their cost with the option to filter by region.

• Select the stacks to import to Terraform and choose the import method. You can also search and filter by resource type.

• Get a 100% verified Terraform code and state file that matches your resource’s configuration.

Benefits of leveraging ControlMonkey’s Terraform Import Engine for Azure:

1. Generate Terraform code in 75% less time.
2. Increase Terraform coverage to 99%.
3. Out-of-the-box automatic custom Terraform Module creation.
4. Save thousands of DevOps hours by eliminating manual Terraform code writing.

Do you have Azure infrastructure that you’re looking to shift to Terraform?
ControlMonkey offers the easiest and most swift way to do it.
Are you interested in learning more and seeing it for yourself? Book a 30-minute technical discussion with our Terraform Experts.

As part of our continuous Enterprise-ready support and in response to our customers’ growing needs, we are happy to announce a massive upgrade to our Onboarding process.
Starting today, ControlMonkey users can Connect an AWS organization with dozens or hundreds of accounts to ControlMonkey with a few clicks.

Instead of onboarding each account individually, which was very time-consuming, Connect an AWS Organization allows you to onboard hundreds of accounts in a few clicks, streamlining the onboarding process.

This capability leverages CloudFormation’s StackSet feature.

The StackSet in your parent (organization) account will generate an IAM Role and IAM Policy (which enable the connection to the ControlMonkey platform) in the organizational units and accounts you choose to opt-in.

With Connect an AWS Organization, ControlMonkey customers with dozens or even hundreds of AWS accounts can shorten the onboarding by 90%, saving precious engineering time and gaining a faster time to value.

Once the entire organization is connected, customers gain a complete cloud inventory of their AWS footprint in minutes!

Our Terraform experts are ready to hop on a 30-minute call  and help you solve your Day 2 challenges.

We are happy to announce that we have reinforced our Terraform Knowledge Hub solution, giving you full visibility into your Terraform Git repository tree.

Since its initial release, we have upgraded our Terraform Explorer Dashboard with many awesome capabilities, such as the Terraform Modules Explorer and the Terraform Providers Explorer.

We often encounter customers who manage large-scale Terraform codebases across multiple Git repositories and various version control systems (GitHub, GitLab, BitBucket, Azure DevOps). These customers struggle to track where their Terraform code resides and determine which code is managed with GitOps methodologies or has drift detection mechanisms in place.

Today, we have added a new view to our Terraform Explorer Dashboard called ‘Code Tree.’
Code Tree scans your Git repos in your version Control System and provides a birds-eye view of:

• Where ControlMonkey detected Terraform/Terragrunt/OpenTofu Code:

• Which sub-directories of code are managed by ControlMonkey Stacks and benefits from Terraform CI/CD, Security Policies, Drift Detection & Remediation and more:

• Which sub-directories are currently not managed by ControlMonkey (aka potential stacks) but can be with a 1-Click:

With Code Tree, ControlMonkey users gain a 30,000-foot view of their entire code-base and understand exactly which parts of their environment are not yet managed by ControlMonkey.

Managing Terraform stacks with ControlMonkey provides the advanced layer of Terraform Automation:

1. Infrastructure CI/CD with Control Policies to enforce security and compliance standards
2. Drift Detection and remediation capabilities to quickly resolve any code discrepancies.

If you have a large-scale Terraform Codebase and you find yourself struggle to manage it efficiently we would love to chat!

Today, ControlMonkey is pleased to announce that we have added the capability to easily import AWS Identity Center resources to Terraform/OpenTofu Code using our Terraform Import Engine.

AWS Identity Center is a service that provides centralized management of access to multiple AWS accounts and applications. It enables organizations to manage user identities and permissions efficiently, allowing users to sign in to their AWS accounts and applications with a single set of credentials

Provisioning Identity Stores resources with Terraform/OpenTofu provides a consistent, version-controlled, simplified, and automated way to manage AWS Accounts permissions and RBAC and reduces the overall risk of manual misconfigurations.

ControlMonkey now supports the one-click Terraform/OpenTofu Import of the following Identity Store resources:

IdentityStore::User (aws_identitystore_user)
IdentityStore::Group (aws_identitystore_group)
IdentityStore::GroupMembership (aws_identitystore_group_membership)
SSO:Assignment(aws_ssoadmin_account_assignment)
SSO:PermissionSet(aws_ssoadmin_permission_set)

Are you using Identity Center and have resources you would like to shift to Terraform?
Feel free to book an intro meeting to learn more about how ControlMonkey generates the Terraform/OpenTofu code that represents your Identity Center configuration, making the shift to Terraform as seamless as possible.