ec2_lc - Create or delete AWS Autoscaling Launch Configurations

Author:Gareth Rushgrove

Synopsis

New in version 1.6.

Can create or delete AwS Autoscaling Configurations Works with the ec2_asg module to manage Autoscaling Groups

Options

parameter required default choices comments
aws_access_key no
    AWS access key. If not set then the value of the AWS_ACCESS_KEY environment variable is used.
    aws_secret_key no
      AWS secret key. If not set then the value of the AWS_SECRET_KEY environment variable is used.
      ec2_url no
        Url to use to connect to EC2 or your Eucalyptus cloud (by default the module will use EC2 endpoints). Must be specified if region is not used. If not set then the value of the EC2_URL environment variable, if any, is used
        image_id no
          The AMI unique identifier to be used for the group
          instance_monitoring no
            whether instances in group are launched with detailed monitoring.
            instance_type yes
              instance type to use for the instance
              key_name no
                The SSH key name to be used for access to managed instances
                name yes
                  Unique name for configuration
                  profile no
                    uses a boto profile. Only works with boto >= 2.24.0 (added in Ansible 1.6)
                    region no
                      The AWS region to use. If not specified then the value of the EC2_REGION environment variable, if any, is used.
                      security_groups no
                        A list of security groups into which instances should be found
                        security_token no
                          security token to authenticate against AWS (added in Ansible 1.6)
                          spot_price no
                            The spot price you are bidding. Only applies for an autoscaling group with spot instances.
                            state yes
                            • present
                            • absent
                            register or deregister the instance
                            user_data no
                              opaque blob of data which is made available to the ec2 instance
                              validate_certs no yes
                              • yes
                              • no
                              When set to "no", SSL certificates will not be validated for boto versions >= 2.6.0. (added in Ansible 1.5)
                              volumes no
                                a list of volume dicts, each containing device name and optionally ephemeral id or snapshot id. Size and type (and number of iops for io device type) must be specified for a new volume or a root volume, and may be passed for a snapshot volume. For any volume, a volume size less than 1 will be interpreted as a request not to create the volume.

                                Note

                                Requires boto

                                Examples


                                - ec2_lc:
                                    name: special
                                    image_id: ami-XXX
                                    key_name: default
                                    security_groups: 'group,group2'
                                    instance_type: t1.micro
                                

                                Note

                                The following environment variables can be used AWS_ACCESS_KEY or EC2_ACCESS_KEY or AWS_ACCESS_KEY_ID, AWS_SECRET_KEY or EC2_SECRET_KEY or AWS_SECRET_ACCESS_KEY, AWS_REGION or EC2_REGION, AWS_SECURITY_TOKEN

                                Note

                                Ansible uses the boto configuration file (typically ~/.boto) if no credentials are provided. See http://boto.readthedocs.org/en/latest/boto_config_tut.html

                                Note

                                AWS_REGION or EC2_REGION can be typically be used to specify the AWS region, when required, but this can also be configured in the boto config file