AWS Service Catalog announces support for additional Infrastructure as Code (IaC) provisioning tools

AWS Service Catalog customers can now create, distribute, and launch AWS resources that are configured using third- party Infrastructure as Code (IaC) tools such as Ansible, Chef, Pulumi, Puppet, and more. Within AWS Service Catalog, customers can use these IaC tools in addition to previously supported AWS CloudFormation and HashiCorp Terraform Cloud configurations.

With the launch of this feature, customers can rely on AWS Service Catalog as a single platform to organize, govern, and distribute their AWS resources without having to migrate or change their preferred IaC tooling. This feature can be used alongside other key capabilities within AWS Service Catalog including access control, tagging, versioning, maintaining least access privilege, and sharing pre-approved resources across thousands of AWS accounts to end-users. End-users, such as data scientists and machine learning engineers, can simply select and deploy resources from a catalog that is shared with them.

To get started, customers can access and launch a generic reference engine. The generic reference engine is required to provision governed resources using the IaC technology (e.g. HashiCorp Terraform, Ansible, Chef, etc.) and AWS Service Catalog. Deploying the reference engine is a one-time set up and can be executed within minutes. Additionally, the generic reference engine can be modified as needed depending on the IaC technology being used.

To learn more about using this feature, go here. The feature is available in all AWS commercial regions where AWS Service Catalog is available, including the AWS GovCloud (US) Regions. For more information about Service Catalog, please visit the AWS Service Catalog product page and documentation.