ec2_local:
private_ip_address # The local private ip address of the current EC2 instance
private_dns_name # The local private dns name of the current EC2 instance
private_dns_name_safe # The shortened safe version of the dns name
ec2_neighbours: # A list of running EC2 instances within this vpc
<ip-address>:
private_dns_name: <private_dns_name>
private_dns_name_safe: <private_dns_name_safe>
lbs: # A dictionary of {lb_name1:{attrs..}, {lb_name2:{attrs..}}
<load-balancer-name>: # A load balancer name that shares the same vpc_id as this instance
# and has this instance's instance_id in its "instances" list.
dns_name: # The dns name of the load balancer as taken from elb
name: # The load balancer resource name (short). This is the same
# as the <load-balancer-name> key name.
scheme: # The type of load balancer eg. internet-facing
security_groups: # A list of the load balancer's security groups
vpc_id: # The vpc_id (also used to filter this instance's load balancers)When asg.py runs on a node, it returns either True or False based on whether the instance is the first instance of the ASG group. It returns True/False when ran as salt call or 0/1 when run as python script.
The premise of asg.py is to provide a mechanism to define things that have to run once per ASG group. Example:
# On first node of ASG group
$ python /srv/salt-formules/_modules/asg.py && echo True
True
# On any other node of ASG group
$ python /srv/salt-formules/_modules/asg.py && echo True
$The above could be used by shell scripts that run on the minions or crontab entries.
Also, it can be used in salt states:
{% if salt['asg.is_first_of_asg_group']() == True %}
postgresql-client:
pkg.installed
{% endif %}Sets grains for elasticache endpoints for a redis type, consisting of a primary (read-write) endpoint, and a list of read-only endpoints. These endpoints will only be collected if there is already a grain ElasticacheReplicationGroupName containing the replication group name.
'elasticache': {
'primary_endpoint': {'address': <address>, 'port': <port>},
'default_endpoint': {'address': <address>, 'port': <port>},
'read_endpoints': [
{'address': <address>, 'port': <port>},
{'address': <address>, 'port': <port>},
{'address': <address>, 'port': <port>}
]
}By specifying a list of elastic ips in the pillar data and running the state aws.autoeips, instances can be setup to automatically poll for available EIP's in the specified list, and, if they do not have an EIP attached, associate with an available one. This can prove useful when there is a group of instances that need to be whitelisted in a firewall by IP, providing a more resilient and automated solution than assigning EIP's manually.
aws:
# A list of eips to attempt to associate with (required)
eips:
- 1.2.3.4
- 5.6.7.8
# File path to autoeip log (optional)
auto_eip_log: /var/log/autoeips.log
# Level of logging output (optional)
log_level': 'INFO'
# Enable or disable the use of standby mode to add and remove
# instances automatically dependent on whether thay have
# acquired an EIP or not
eip_enable_standby_mode: True
# Enable or disable the use of failover mode to add and remove
# instances automatically dependent on whether thay have
# acquired an EIP or not. This is the same as stnadby mode but
# does not alert.
eip_enable_failover_mode: FalseNote if the standby mode function is enabled, this requires an additional set of IAM permissions. The following EC2 permissions are required.
"ec2:AssociateAddress",
"ec2:DescribeAddresses",The autoscaling permissions are required if the standby functionality is enabled.
"autoscaling:EnterStandby",
"autoscaling:ExitStandby"The aws.awslogs state sets up the awslogs agent on the instance. It configures a number of common log paths by default. See http://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/QuickStartEC2Instance.html
Note, the instance role must have permissions to work with CloudWatch,
{
"Effect": "Allow",
"Action": [
"logs:CreateLogGroup",
"logs:CreateLogStream",
"logs:PutLogEvents",
"logs:DescribeLogStreams"
],
"Resource": [
"arn:aws:logs:*:*:*"
]
}The following covers some of the pillar options available, in general the defaults should be enough in most cases.
aws:
awslogs:
# A dictionary of log group name to log path entries
# There are a number of common paths provided by default
log_files:
<log_group_name>: <log_file_path>
<log_group_name>: <log_file_path>
# The log group prefix override, this defaults to the stack name.
log_group_prefix: my-stack-name
# The grain to use as the stream id, defaults to instance id
log_stream_id_grain: aws_instance_id