Deploying StackSets to OUs with nested OUs

Hello there!

I have tested the use-case that you mentioned where deployments are made on an OU having only OUs as children but no accounts. However, I haven’t received any errors as such by doing so. Moreover if one or more child OUs are actually empty in the specified OU, there will be no errors thrown by CloudFormation and deploys to OUs that have accounts. (If auto deployment is enabled, for any new accounts added to the empty OUs targeted by the StackSets, a CREATE stack instance operation will be initiated).

Finally you can make use of Account Filter Type while deploying to have a much better control on deployments to limit deployment targets to individual accounts or include additional accounts with provided AWS Organizations units (OUs) with your Create, Update, or Delete operations.