...
| Code Block |
|---|
################################################################################ # Amazon services properties # use.aws: 0=false, 1=trueIf deployed on an EC2 cluster set this to 1: use.aws=1 # S3This is the root s3 bucket name to be used for backups: the# The "s3.url" parameter corresponds to the "S3ROOT" described in "Step 1" above s3.url=infinite.myorg.com |
...
| Code Block |
|---|
################################################################################ # Amazon AWS Settings ################################################################################ # AWS keys (only needed if use.aws=1) aws.access.key=ACCESS_KEY aws.secret.key=SECRET_KEY # Used for s3cmd, see their web page for details s3.gpg.passphrase=none |
Obviously these should be set to your Amazon keys.
Cluster information
| Code Block |
|---|
################################################################################ # Cluster name and URL # Any unique name within the EC2 cluster/subnet: # eg infinite-cluster1 elastic.cluster=CLUSTER_NAME ################################################################################ # Discovery mode = ec2 (if running on AWS) or zen (specify a list of IPs below): elastic.node.discovery=ec2 # (once "elastic.node.discovery" has been set to "ec2", "elastic.search.nodes" can be ignored - the discovery will happen automatically) #elastic.search.nodes= # Also these DB configuration params can be ignored: ################################################################################ # MongoDB Properties #db.cluster.subnet= #db.config.servers= #db.replica.sets= |
In EC2 mode, the "elastic.cluster" string must be the same for all nodes (API and DB) in the cluster. It controls three things:
...