...
- ClusterName: the cluster name, should match the "infinit.e.configuration.properties" file.
- IsConfigSvr: should be set to "1" for the first node created, "0" after that (for combined config server/DB scenarios only
- ReplicaSetIds: For unsharded deployments (as set in "infinit.e.configuration.properties"; almost certainly what you will be running), just leave as 0 all the time. For sharded deployments, use "01" for the first 2 nodes, "12" for the second 2 nodes, etc.
- It is also possible to make a node join multiple replica sets by setting a comma-separated list, eg "0,1,2,3" to belong to 3 replica sets (one DB process is created per replica set). This is not recommended for typical usage, but could be useful eg to use a single node for multiple "slaves" (the low performance won't matter because there'll never be queried in practice)
- NodeName: The name displayed in the EC2 instances
- ConfigFileS3Path: the location of the "infinit.e.configuration.properties" file in your S3 storage.
- AwsAccessId: The AWS ID/Access Key for your Amazon account.
- AwsAccessKey: The AWS Key/Secret Key for your Amazon account.
- AvailabilityZone: Must be consistent with the availability zone from which the stack was launched (top left of CloudFormation tab)
- SecurityGroups: Set the security group from Step 1.
- KeyName: Set the key from Step 1.
...