Using this as a Stack Set template and passing null values

[wallentx]

I was speaking with AWS support, and they suggested that I open an issue here.

I have multiple accounts in AWS Organizations, and the individual accounts in each OU need to have their own specific parameters. I'm using this template as the Stack Set, since it provides a good starting point to act as a boilerplate for provisioning the Network layer of things.

As an example, I'd like to have a single template as the Stack Set, and bind:

"account A" to "params-A.yaml" where VPC=192.168.0.0/16, PrivateSubnet=4, PublicSubnet=0, PrivateAZ1=...

and

"account B" to "params-B.yaml" where VPC=100.64.0.0/16, PrivateSubnet=2, PublicSubnet=2, PrivateAZ1=...

all while my master account simply has the Stack Set staged, and nothing is deployed until I "create-stack-instances" providing the overriding parameters file.

I understand that in order to create a Stack Set, it has to at least attempt to deploy something, and a Stack Set can exist (with errors) if the initial IAM permissions or Cloud Formation template fails.

Is it possible to pass "null" values for the parameters in this template somehow? As in, "Ref" : "AWS::NoValue" for every parameter, or to tell it to essentially "Do nothing" if a parameter value is "null" so that the initial creation of the Stack Set is executed with 0 outputs, but not listed as a failure?

Please let me know if I should be directing this question elsewhere.

[bigpafik]

I had same issue with yaml file I just loaded json and it resolve it Play with file formats. Use Cloudformation designer to convert file format

[tlindsay42]

Closing due to inactivity and we have no intention of supporting a JSON format template again