@stocky-spoon-28903 We found the issue; I was using

securityGroups

instead of

vpcSecurityGroupIds

. Switching to the latter resolves the problem.