Ansible/EC2/Static Inventory - Revision history

Admin: /* Specifying the SSH key */

2018-11-11T17:34:28Z

Specifying the SSH key

← Older revision		Revision as of 17:34, 11 November 2018
Line 48:		Line 48:
	<pre>		<pre>
	[webservers]		[webservers]
	wolf ansible_port=222 ansible_host=8.9.10.11 ansible_user=ubuntu ansible_private_key_file=~~awspk~~		wolf ansible_port=222 ansible_host=8.9.10.11 ansible_user=ubuntu ansible_private_key_file=/home/charles/auth/aws/my-awesome-ssh-key.pem
	eagle ansible_port=22 ansible_host=8.9.10.12 ansible_user=ubuntu ansible_private_key_file=~~awspk~~		eagle ansible_port=22 ansible_host=8.9.10.12 ansible_user=ubuntu ansible_private_key_file=/home/charles/auth/aws/my-awesome-ssh-key.pem
			</pre>

	~~[webserver~~:~~vars]~~		Easier: modify <code>ansible.cfg</code> to define default values for the private key:
	~~awspk~~=/home/charles/auth/aws/my-awesome-ssh-key.pem
			<pre>
			private_key_file=/home/charles/auth/aws/my-awesome-ssh-key.pem
	</pre>		</pre>

Admin: /* Flags */

2018-11-11T16:41:16Z

Flags

← Older revision		Revision as of 16:41, 11 November 2018
Line 58:		Line 58:

	{{AnsibleFlag}}		{{AnsibleFlag}}

			[[Category:AWS]]

Admin: /* Flags */

2018-11-11T16:26:45Z

Flags

← Older revision		Revision as of 16:26, 11 November 2018
Line 55:		Line 55:
	</pre>		</pre>

	=Flags=		==Flags==

	{{AnsibleFlag}}		{{AnsibleFlag}}

Admin: /* Specifying the SSH key */

2018-11-11T16:26:30Z

Specifying the SSH key

← Older revision		Revision as of 16:26, 11 November 2018
Line 54:		Line 54:
	awspk=/home/charles/auth/aws/my-awesome-ssh-key.pem		awspk=/home/charles/auth/aws/my-awesome-ssh-key.pem
	</pre>		</pre>

			=Flags=

			{{AnsibleFlag}}

Admin: /* Specifying the SSH key */

2018-11-11T04:49:51Z

Specifying the SSH key

← Older revision		Revision as of 04:49, 11 November 2018
Line 45:		Line 45:

	Example:		Example:

	~~<pre>~~

	<pre>		<pre>

Admin: /* Specifying the SSH key */

2018-11-11T04:49:39Z

Specifying the SSH key

← Older revision		Revision as of 04:49, 11 November 2018
Line 42:		Line 42:
	When you set up your nodes with AWS, you are required to set up an SSH key pair, for which you are given the private key by Amazon and the public key is stored on the remote server, allowing you to SSH into the server.		When you set up your nodes with AWS, you are required to set up an SSH key pair, for which you are given the private key by Amazon and the public key is stored on the remote server, allowing you to SSH into the server.

	<~~pre~~>ansible_private_key_file</code> must be used to specify the location of this Amazon-provided private key, either on a machine-by-machine basis, or by setting a group variable.		<code>ansible_private_key_file</code> must be used to specify the location of this Amazon-provided private key, either on a machine-by-machine basis, or by setting a group variable.

	Example:		Example:

Admin: Created page with "{{Main|Ansible/EC2}} This page covers how to manage a static inventory file (hosts file) by hand. ==Static vs dynamic inventory== Ansible/EC2/Static Inventory - static..."

2018-11-11T04:49:21Z

Created page with "{{Main|Ansible/EC2}} This page covers how to manage a static inventory file (hosts file) by hand. ==Static vs dynamic inventory== Ansible/EC2/Static Inventory - static..."

New page

{{Main|Ansible/EC2}}

This page covers how to manage a static inventory file (hosts file) by hand.

==Static vs dynamic inventory==

[[Ansible/EC2/Static Inventory]] - static inventory requires the hosts file (containing the list of machines that Ansible is managing) be kept up to date by hand. This can be a burden if details are changing often or if resources are allocated automatically.

[[Ansible/EC2/Dynamic Inventory]] - dynamic inventory uses the AWS API to get information about machines that AWS is managing.

==Managing a static inventory file using EC2==

Edit <code>playbooks/hosts</code> and include details about each AWS host. It is convenient to use the same SSH key for all machines.

If you are managing the hosts file by hand, you may want to create groups: [[Ansible/Groups]]

===Specifying the hostname and port===

The hosts file can contain domain names directly, grouped by bracketed group names - for example, if you already have DNS records for your subdomains set up to point to your EC2 nodes, you can do something like this:

<pre>
[webservers]
california.example.com
newyork.example.com
florida.example.com:222
</pre>

If no port listed, Ansible assumes a default SSH port of 22. For non-standard ports (like florida.example.com) use a colon and the port where the SSH service is listening.

If you have a public IP address for the machine but no domain, you can use an alias for the machine:

<pre>
[webservers]
wolf ansible_port=222 ansible_host=8.9.10.11 ansible_user=ubuntu
eagle ansible_port=22 ansible_host=8.9.10.12 ansible_user=ubuntu
</pre>

The <code>ansible_user</code> parameter can be used to set the user that Ansible logs in as, by default. On AWS Ubuntu images, the ubuntu user is already set up and has passwordless sudo access, and is a wise choice.

===Specifying the SSH key===

When you set up your nodes with AWS, you are required to set up an SSH key pair, for which you are given the private key by Amazon and the public key is stored on the remote server, allowing you to SSH into the server.

<pre>ansible_private_key_file</code> must be used to specify the location of this Amazon-provided private key, either on a machine-by-machine basis, or by setting a group variable.

Example:

<pre>

<pre>
[webservers]
wolf ansible_port=222 ansible_host=8.9.10.11 ansible_user=ubuntu ansible_private_key_file=awspk
eagle ansible_port=22 ansible_host=8.9.10.12 ansible_user=ubuntu ansible_private_key_file=awspk

[webserver:vars]
awspk=/home/charles/auth/aws/my-awesome-ssh-key.pem
</pre>