Currently all the example and template files include all the mandatory values, including the instance ID, VPC and subnets. It seems a bit odd to put the ID, VPC and subnets in the configuration files, when these will be set at deployment time. When using the scripts you always need to pass them in explicitly. We could remove the need to include these in a configuration file set by the user at all, while still including them in the config bucket.
It might also be worth explaining explicitly in the property descriptions when they are usually set as deployment parameters rather than in the properties file. We can probably leave those ones out of the basic example.
Currently all the example and template files include all the mandatory values, including the instance ID, VPC and subnets. It seems a bit odd to put the ID, VPC and subnets in the configuration files, when these will be set at deployment time. When using the scripts you always need to pass them in explicitly. We could remove the need to include these in a configuration file set by the user at all, while still including them in the config bucket.
It might also be worth explaining explicitly in the property descriptions when they are usually set as deployment parameters rather than in the properties file. We can probably leave those ones out of the basic example.