- Newest
- Most votes
- Most comments
That is correct, you will need to deploy the AWS Service Catalog Engine for Terraform in each region which you wish to deploy Service Catalog products. Service Catalog expects certain resources to exist within the region including SQS queues and Lambda functions in order to support provisioning products using the EXTERNAL product type. If you have not completed setup in the region, you will an error similar to the following when you try to provision a product of this type.
Service Catalog is not authorized to perform: lambda:InvokeFunction on resource: arn:aws:lambda:<REGION>:<ACCOUNT_ID>:function:ServiceCatalogExternalParameterParser because no resource-based policy allows the lambda:InvokeFunction action or the lambda does not exist in account ACCOUNT_ID.
Without further details on your use case and what you are trying to accomplish, I cannot provide an informed opinion on whether or not to use Service Catalog with Terraform. One callout is that the AWS Service Catalog Engine for Terraform provisions products in a single-region and out-of-the-box will override your provider configuration with the region of the provisioned product. This makes the behavior similar to CloudFormation. As such, if you need a single Terraform configuration to deploy resources to multiple regions, the Service Catalog may not be the best fit.
Relevant content
- Accepted Answerasked 2 years ago
- asked 5 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated a year ago
thank you, it was helpfull