mirror of https://github.com/ansible/ansible.git
Docs: Moves the AWS Scenario Guide out of the main docs (#74704)
* removes AWS scenario guide, moving to collection * first attept to replace TOC entries * not sure what I did, but saving it * updates TOCs to reflect new location of aws guide * reinstates original page as a stub * adds links to new location for AWS guide, updates header Co-authored-by: Alicia Cozine <acozine@users.noreply.github.com>pull/75930/head
Alicia Cozine
3 years ago
committed by
GitHub
parent
2f531d73dd
commit
9a4346bae3
@ -1,284 +1,6 @@
|
||||
:orphan:
|
||||
|
||||
Amazon Web Services Guide
|
||||
=========================
|
||||
|
||||
.. _aws_intro:
|
||||
|
||||
Introduction
|
||||
````````````
|
||||
|
||||
Ansible contains a number of modules for controlling Amazon Web Services (AWS). The purpose of this
|
||||
section is to explain how to put Ansible modules together (and use inventory scripts) to use Ansible in AWS context.
|
||||
|
||||
Requirements for the AWS modules are minimal.
|
||||
|
||||
All of the modules require and are tested against recent versions of botocore and boto3. Starting with the 2.0 AWS collection releases, it is generally the policy of the collections to support the versions of these libraries released 12 months prior to the most recent major collection revision. Individual modules may require a more recent library version to support specific features or may require the boto library, check the module documentation for the minimum required version for each module. You must have the boto3 Python module installed on your control machine. You can install these modules from your OS distribution or using the python package installer: ``pip install boto3``.
|
||||
|
||||
Starting with the 2.0 releases of both collections, Python 2.7 support will be ended in accordance with AWS' `end of Python 2.7 support <https://aws.amazon.com/blogs/developer/announcing-end-of-support-for-python-2-7-in-aws-sdk-for-python-and-aws-cli-v1/>`_ and Python 3.6 or greater will be required.
|
||||
|
||||
|
||||
Whereas classically Ansible will execute tasks in its host loop against multiple remote machines, most cloud-control steps occur on your local machine with reference to the regions to control.
|
||||
|
||||
In your playbook steps we'll typically be using the following pattern for provisioning steps::
|
||||
|
||||
- hosts: localhost
|
||||
gather_facts: False
|
||||
tasks:
|
||||
- ...
|
||||
|
||||
.. _aws_authentication:
|
||||
|
||||
Authentication
|
||||
``````````````
|
||||
|
||||
Authentication with the AWS-related modules is handled by either
|
||||
specifying your access and secret key as ENV variables or module arguments.
|
||||
|
||||
For environment variables::
|
||||
|
||||
export AWS_ACCESS_KEY_ID='AK123'
|
||||
export AWS_SECRET_ACCESS_KEY='abc123'
|
||||
|
||||
For storing these in a vars_file, ideally encrypted with ansible-vault::
|
||||
|
||||
---
|
||||
ec2_access_key: "--REMOVED--"
|
||||
ec2_secret_key: "--REMOVED--"
|
||||
|
||||
Note that if you store your credentials in vars_file, you need to refer to them in each AWS-module. For example::
|
||||
|
||||
- ec2
|
||||
aws_access_key: "{{ec2_access_key}}"
|
||||
aws_secret_key: "{{ec2_secret_key}}"
|
||||
image: "..."
|
||||
|
||||
.. _aws_provisioning:
|
||||
|
||||
Provisioning
|
||||
````````````
|
||||
|
||||
The ec2 module provisions and de-provisions instances within EC2.
|
||||
|
||||
An example of making sure there are only 5 instances tagged 'Demo' in EC2 follows.
|
||||
|
||||
In the example below, the "exact_count" of instances is set to 5. This means if there are 0 instances already existing, then
|
||||
5 new instances would be created. If there were 2 instances, only 3 would be created, and if there were 8 instances, 3 instances would
|
||||
be terminated.
|
||||
|
||||
What is being counted is specified by the "count_tag" parameter. The parameter "instance_tags" is used to apply tags to the newly created
|
||||
instance.::
|
||||
|
||||
# demo_setup.yml
|
||||
|
||||
- hosts: localhost
|
||||
gather_facts: False
|
||||
|
||||
tasks:
|
||||
|
||||
- name: Provision a set of instances
|
||||
ec2:
|
||||
key_name: my_key
|
||||
group: test
|
||||
instance_type: t2.micro
|
||||
image: "{{ ami_id }}"
|
||||
wait: true
|
||||
exact_count: 5
|
||||
count_tag:
|
||||
Name: Demo
|
||||
instance_tags:
|
||||
Name: Demo
|
||||
register: ec2
|
||||
|
||||
The data about what instances are created is being saved by the "register" keyword in the variable named "ec2".
|
||||
|
||||
From this, we'll use the add_host module to dynamically create a host group consisting of these new instances. This facilitates performing configuration actions on the hosts immediately in a subsequent task.::
|
||||
|
||||
# demo_setup.yml
|
||||
|
||||
- hosts: localhost
|
||||
gather_facts: False
|
||||
|
||||
tasks:
|
||||
|
||||
- name: Provision a set of instances
|
||||
ec2:
|
||||
key_name: my_key
|
||||
group: test
|
||||
instance_type: t2.micro
|
||||
image: "{{ ami_id }}"
|
||||
wait: true
|
||||
exact_count: 5
|
||||
count_tag:
|
||||
Name: Demo
|
||||
instance_tags:
|
||||
Name: Demo
|
||||
register: ec2
|
||||
|
||||
- name: Add all instance public IPs to host group
|
||||
add_host: hostname={{ item.public_ip }} groups=ec2hosts
|
||||
loop: "{{ ec2.instances }}"
|
||||
|
||||
With the host group now created, a second play at the bottom of the same provisioning playbook file might now have some configuration steps::
|
||||
|
||||
# demo_setup.yml
|
||||
|
||||
- name: Provision a set of instances
|
||||
hosts: localhost
|
||||
# ... AS ABOVE ...
|
||||
|
||||
- hosts: ec2hosts
|
||||
name: configuration play
|
||||
user: ec2-user
|
||||
gather_facts: true
|
||||
|
||||
tasks:
|
||||
|
||||
- name: Check NTP service
|
||||
service: name=ntpd state=started
|
||||
|
||||
.. _aws_security_groups:
|
||||
|
||||
Security Groups
|
||||
```````````````
|
||||
|
||||
Security groups on AWS are stateful. The response of a request from your instance is allowed to flow in regardless of inbound security group rules and vice-versa.
|
||||
In case you only want allow traffic with AWS S3 service, you need to fetch the current IP ranges of AWS S3 for one region and apply them as an egress rule.::
|
||||
|
||||
- name: fetch raw ip ranges for aws s3
|
||||
set_fact:
|
||||
raw_s3_ranges: "{{ lookup('aws_service_ip_ranges', region='eu-central-1', service='S3', wantlist=True) }}"
|
||||
|
||||
- name: prepare list structure for ec2_group module
|
||||
set_fact:
|
||||
s3_ranges: "{{ s3_ranges | default([]) + [{'proto': 'all', 'cidr_ip': item, 'rule_desc': 'S3 Service IP range'}] }}"
|
||||
loop: "{{ raw_s3_ranges }}"
|
||||
|
||||
- name: set S3 IP ranges to egress rules
|
||||
ec2_group:
|
||||
name: aws_s3_ip_ranges
|
||||
description: allow outgoing traffic to aws S3 service
|
||||
region: eu-central-1
|
||||
state: present
|
||||
vpc_id: vpc-123456
|
||||
purge_rules: true
|
||||
purge_rules_egress: true
|
||||
rules: []
|
||||
rules_egress: "{{ s3_ranges }}"
|
||||
tags:
|
||||
Name: aws_s3_ip_ranges
|
||||
|
||||
.. _aws_host_inventory:
|
||||
|
||||
Host Inventory
|
||||
``````````````
|
||||
|
||||
Once your nodes are spun up, you'll probably want to talk to them again. With a cloud setup, it's best to not maintain a static list of cloud hostnames
|
||||
in text files. Rather, the best way to handle this is to use the aws_ec2 inventory plugin. See :ref:`dynamic_inventory`.
|
||||
|
||||
The plugin will also return instances that were created outside of Ansible and allow Ansible to manage them.
|
||||
|
||||
.. _aws_tags_and_groups:
|
||||
|
||||
Tags And Groups And Variables
|
||||
`````````````````````````````
|
||||
|
||||
When using the inventory plugin, you can configure extra inventory structure based on the metadata returned by AWS.
|
||||
|
||||
For instance, you might use ``keyed_groups`` to create groups from instance tags::
|
||||
|
||||
plugin: aws_ec2
|
||||
keyed_groups:
|
||||
- prefix: tag
|
||||
key: tags
|
||||
|
||||
|
||||
You can then target all instances with a "class" tag where the value is "webserver" in a play::
|
||||
|
||||
- hosts: tag_class_webserver
|
||||
tasks:
|
||||
- ping
|
||||
|
||||
You can also use these groups with 'group_vars' to set variables that are automatically applied to matching instances. See :ref:`splitting_out_vars`.
|
||||
|
||||
.. _aws_pull:
|
||||
|
||||
Autoscaling with Ansible Pull
|
||||
`````````````````````````````
|
||||
|
||||
Amazon Autoscaling features automatically increase or decrease capacity based on load. There are also Ansible modules shown in the cloud documentation that
|
||||
can configure autoscaling policy.
|
||||
|
||||
When nodes come online, it may not be sufficient to wait for the next cycle of an ansible command to come along and configure that node.
|
||||
|
||||
To do this, pre-bake machine images which contain the necessary ansible-pull invocation. Ansible-pull is a command line tool that fetches a playbook from a git server and runs it locally.
|
||||
|
||||
One of the challenges of this approach is that there needs to be a centralized way to store data about the results of pull commands in an autoscaling context.
|
||||
For this reason, the autoscaling solution provided below in the next section can be a better approach.
|
||||
|
||||
Read :ref:`ansible-pull` for more information on pull-mode playbooks.
|
||||
|
||||
.. _aws_autoscale:
|
||||
|
||||
Autoscaling with Ansible Tower
|
||||
``````````````````````````````
|
||||
|
||||
:ref:`ansible_tower` also contains a very nice feature for auto-scaling use cases. In this mode, a simple curl script can call
|
||||
a defined URL and the server will "dial out" to the requester and configure an instance that is spinning up. This can be a great way
|
||||
to reconfigure ephemeral nodes. See the Tower install and product documentation for more details.
|
||||
|
||||
A benefit of using the callback in Tower over pull mode is that job results are still centrally recorded and less information has to be shared
|
||||
with remote hosts.
|
||||
|
||||
.. _aws_cloudformation_example:
|
||||
|
||||
Ansible With (And Versus) CloudFormation
|
||||
````````````````````````````````````````
|
||||
|
||||
CloudFormation is a Amazon technology for defining a cloud stack as a JSON or YAML document.
|
||||
|
||||
Ansible modules provide an easier to use interface than CloudFormation in many examples, without defining a complex JSON/YAML document.
|
||||
This is recommended for most users.
|
||||
|
||||
However, for users that have decided to use CloudFormation, there is an Ansible module that can be used to apply a CloudFormation template
|
||||
to Amazon.
|
||||
|
||||
When using Ansible with CloudFormation, typically Ansible will be used with a tool like Packer to build images, and CloudFormation will launch
|
||||
those images, or ansible will be invoked through user data once the image comes online, or a combination of the two.
|
||||
|
||||
Please see the examples in the Ansible CloudFormation module for more details.
|
||||
|
||||
.. _aws_image_build:
|
||||
|
||||
AWS Image Building With Ansible
|
||||
```````````````````````````````
|
||||
|
||||
Many users may want to have images boot to a more complete configuration rather than configuring them entirely after instantiation. To do this,
|
||||
one of many programs can be used with Ansible playbooks to define and upload a base image, which will then get its own AMI ID for usage with
|
||||
the ec2 module or other Ansible AWS modules such as ec2_asg or the cloudformation module. Possible tools include Packer, aminator, and Ansible's
|
||||
ec2_ami module.
|
||||
|
||||
Generally speaking, we find most users using Packer.
|
||||
|
||||
See the Packer documentation of the `Ansible local Packer provisioner <https://www.packer.io/docs/provisioners/ansible/ansible-local>`_ and `Ansible remote Packer provisioner <https://www.packer.io/docs/provisioners/ansible/ansible>`_.
|
||||
|
||||
If you do not want to adopt Packer at this time, configuring a base-image with Ansible after provisioning (as shown above) is acceptable.
|
||||
|
||||
.. _aws_next_steps:
|
||||
|
||||
Next Steps: Explore Modules
|
||||
```````````````````````````
|
||||
|
||||
Ansible ships with lots of modules for configuring a wide array of EC2 services. Browse the "Cloud" category of the module
|
||||
documentation for a full list with examples.
|
||||
|
||||
.. seealso::
|
||||
|
||||
:ref:`list_of_collections`
|
||||
Browse existing collections, modules, and plugins
|
||||
:ref:`working_with_playbooks`
|
||||
An introduction to playbooks
|
||||
:ref:`playbooks_delegation`
|
||||
Delegation, useful for working with loud balancers, clouds, and locally executed steps.
|
||||
`User Mailing List <https://groups.google.com/group/ansible-devel>`_
|
||||
Have a question? Stop by the google group!
|
||||
:ref:`communication_irc`
|
||||
How to join Ansible chat channels
|
||||
The content on this page has moved. Please see the updated :ref:`ansible_collections.amazon.aws.docsite.aws_intro` in the AWS collection.
|
||||
|
||||
Loading…
Reference in New Issue