In CloudFormation both nested stacks and modules encourage reusability by creating common components. From the AWS documentation it is not coming out when to us
uca
python-routes
apache-spark-ml
klaxon
volume-shadow-service
pthread-barriers
dataguard
magickwand
hardware-interface
skeffectnode
bzip
tracemalloc
wbem
android-device-manager
stage
d3-graphviz
blazer
rcurl
snmptrapd
stable-baselines
protoc-gen-openapiv2
pod-install
sql-order-by
zend-loader
compareobject
effective-java
patch-package
node.js-buffer
google-cloud-intellij
invalid-argument