This setting is # dependent upon the AMI that is used to deploy. # securitygroup : default # Optionally configure default region # location : ap-southeast-1 availability_zone : ap-southeast-1b # Configure which user to use to run the deploy script. It might cause an error message which says that network # interfaces and an instance-level security groups may not be specified # on the same request. # private_key : /etc/salt/my_test_key.pem keyname : my_test_key # This one should NOT be specified if VPC was not configured in AWS to be # the default. This defaults to 10 retries # with a one second delay betwee retries win_deploy_auth_retries : 10 win_deploy_auth_retry_delay : 1 # Set the EC2 access credentials (see below) # id : 'use-instance-role-credentials' key : 'use-instance-role-credentials' # Make sure this key is owned by root with permissions 0400.
# Valid options are: # private_ips - The salt-master is also hosted with EC2 # public_ips - The salt-master is hosted outside of EC2 # ssh_interface : private_ips # Optionally configure the Windows credential validation number of # retries and delay between retries.
Typical users # are: # Amazon Linux -> ec2-user # RHEL -> ec2-user # CentOS -> ec2-user # Ubuntu -> ubuntu # Debian -> admin # ssh_username : ec2-user # Optionally add an IAM profile iam_profile : 'arn:aws:iam::123456789012:instance-profile/ExampleInstanceProfile' driver : ec2 my-ec2-southeast-private-ips : # Set up the location of the salt master # minion : master : # Specify whether to use public or private IP for deploy script. It is usually safer to # configure this individually in a profile, than globally. # private_key : /etc/salt/my_test_key.pem keyname : my_test_key securitygroup : default # Optionally configure default region # Use salt-cloud -list-locations to obtain valid regions # location : ap-southeast-1 availability_zone : ap-southeast-1b # Configure which user to use to run the deploy script.
role_arn : arn:aws:iam::012345678910:role/SomeRoleName # Make sure this key is owned by corresponding user (default 'salt') with permissions 0400. This defaults to 10 retries # with a one second delay betwee retries win_deploy_auth_retries : 10 win_deploy_auth_retry_delay : 1 # Set the EC2 access credentials (see below) # id : 'use-instance-role-credentials' key : 'use-instance-role-credentials' # If 'role_arn' is specified the above credentials are used to # to assume to the role. # Valid options are: # private_ips - The salt-cloud command is run inside the EC2 # public_ips - The salt-cloud command is run outside of EC2 # ssh_interface : public_ips # Optionally configure the Windows credential validation number of # retries and delay between retries. my-ec2-southeast-public-ips : # Set up the location of the salt master # minion : master : # Set up grains information, which will be common for all nodes # using this provider grains : node_type : broker release : 1.0.1 # Specify whether to use public or private IP for deploy script. # Note: This example is for /etc/salt/cloud.providers or any file in the # /etc/salt// directory.