Why OOB Cloud Services Catalog is designed to work only via Terraform?

[Suggy]

There are OOB Cloud Services Catalog items for AWS, Azure etc but it works via Terraform.

Why so? Reason behind that?

Does ServiceNow want to forcefully make customer to use Terraform to enjoy OOB items?

What if customer is not using terraform or any other infrastructure management tools? of what if customer is using Ansible for example?

They cannot use OOB items then?

[Swapna Abburi]

Hi @Suggy 

May be OOTB cloud catalog items are using Terraform however, we can create catalog items using other IaC tools as well. We used Azure ARM templates in my previous CPG implementation.

[Suggy]

Hi @Swapna Abburi Thats exactly I was wondering why ServiceNow has chosen Terraform for all the OOB catalog items. ServiceNow by end of Day 2, users should be ready to start provisioning the cloud resources using extensive OOB catalog items, but that is not for all.

[Ram Devanathan1]

great question @Suggy and  @Swapna Abburi 

The answer is - for this demo content catalog items, we wanted to use free tech that's common to multiple clouds. Note that the word 'demo' content is meant as a sample reference, not production grade - e.g., we've used some policies here that may not work for your organization. e.g., approval is only single level, or the ACC must be installed if the environment is prod.