Product provisioning specifications

Service Catalog initiates the provisioning process as a CloudFormation stack set deployment of the resources that are specified in the CloudFormation provisioning template. (The template can be created directly in AWS CloudFormation or generated by the AWS CDK ProductStack construct.) Service Catalog product provisioning is a closed process—you cannot customize it to add preliminary or post-process steps, or tune it. However, you can modify the provisioning template to add steps in the form of CloudFormation resource specifications. These could be AWS Lambda or AWS Step Functions, or Lambda-backed custom resources that perform preliminary steps (such as custom bootstrapping to set up a bastion host that is used during provisioning) and post-steps (such as tearing down the bastion host). This method of implementing pre-provisioning and post-provisioning steps is subject to the same include and nested stack restrictions as the provisioning template.

You can specify target accounts as individual accounts, not as organizational units (OUs). You can write a custom resource or function to work around this limitation. Most organizations provision portfolios of products to OUs and not to individual accounts, because they automate the generation of accounts and don’t want to maintain account lists manually.