AWS and HashiCorp jointly announce the launch of a new integration between AWS Service Catalog and HashiCorp Terraform Cloud to enable large enterprises on AWS.
Earlier in 2023, Amazon Web Services announced AWS Service Catalog support for Terraform Community. Today, HashiCorp and AWS have announced AWS Service Catalog support for Terraform Cloud. Customers can now take advantage of the advanced governance and visibility features in their Terraform workflows by linking their Service Catalog product provisioning to HashiCorp’s Terraform Cloud.
Customers can now use AWS Service Catalog as the single tool to organize, govern, and distribute their Terraform Cloud configurations within AWS at scale. This includes integrated access to key AWS Service Catalog features, including cataloging of standardized and pre-approved Terraform configurations, infrastructure as code templates, access control, resource provisioning with least-privilege access, versioning, sharing to thousands of AWS accounts, and tagging.
The new feature allows administrators to curate a portfolio of pre-approved Terraform configurations on AWS Service Catalog. This enables end users like engineers, database administrators, and data scientists to deploy these Terraform configurations with a single action from the AWS interface. By combining Terraform Cloud with AWS Service Catalog, we’re combining a self-service interface that many customers are familiar with, AWS Service Catalog, with the existing workflows and policy guardrails of Terraform Cloud.
End users can easily queue a Terraform configuration from the AWS Service Catalog interface, which generates a workspace for that workload and triggers a run on Terraform Cloud. As credentials are required to initiate a run, the project is configured with dynamic provider credentials, which automatically authenticates the workspace to plan or apply the queued Terraform configuration. Once authenticated, the Terraform configuration provisions the desired resources on AWS. The end user never has to interface with Terraform Cloud or handle static credentials throughout the workflow.
To initiate this feature, you can start by using the AWS Service Catalog Engine for Terraform Cloud provided by HashiCorp on GitHub and following the setup instructions provided in its README. You’ll need a Terraform Cloud organization that supports Team Management. Everything else needed to get set up is included in the project's Terraform configuration. If you run into any setup troubles along the way, the README also includes troubleshooting steps that should help resolve common issues that you may encounter.
The AWS Service Catalog Engine for Terraform Cloud is an integration that allows product cataloging and provisioning using Terraform. With the engine installed into your account, the necessary code and infrastructure to integrate the Terraform Cloud engine with AWS Service Catalog will automatically be configured. The setup can be completed in just a few minutes, and it needs to be done only once. Once the setup is complete, you can immediately start using AWS Service Catalog to develop and manage AWS Service Catalog products, and make them accessible to your end users across all your accounts.
Using Terraform Cloud through the AWS Service Catalog interface
HashiCorp Terraform is the world’s most widely used multi-cloud provisioning product. The Terraform ecosystem has more than 3,000 providers, 14,000 modules, and 250 million downloads. Terraform Cloud is the fastest way to adopt Terraform, providing everything practitioners, teams, and global businesses need to create and collaborate on infrastructure and manage risks for security, compliance, and operational constraints.
If you are currently using Terraform Community or are completely new to Terraform, you can sign up for Terraform Cloud and get started using the Free offering today.
Streamlined run task reviews provide meaningful context on run task evaluations to help practitioners resolve issues faster without having to leave Terraform Cloud.
No-code provisioning adds more Day 2 operations. Users can now update the module version used in their no-code workspaces.
Terraform Enterprise now supports more flexible deployment options for self-hosted environments, including cloud-managed Kubernetes services.