Ansible-Setup

Tested on:

Structure

.
├── ansible.cfg
├── keypair.pem
├── ec2.ini
├── ec2.py
└── hosts

Freatures

Installing and Configuring Ansible on multiple OS without knowing internal.
Setting up Ansible for EC2 with Dynamic Inventory.

Pre-requisite

Python3
Git

Installation

Install Python3 and Git on controller node.

sudo yum install python3 git -y       # for RHEL/Centos

sudo apt install python3 git -y       # for ubuntu
sudo apt-get -y install python3-pip

Clone this repository and go inside it.

git clone https://github.com/hackcoderr/ansible-setup.git
cd ansible-setup/

Run the script.py file to install the ansible.

python3 script.py

How to configure dynamic Inventory

Open ec2.ini file and give access key and secret key of your AWS IAM User at the bottom of ec2.ini file.

sudo vi /etc/ansible/ec2.ini

[credentials]

# The AWS credentials can optionally be specified here. Credentials specified
# here are ignored if the environment variable AWS_ACCESS_KEY_ID or
# AWS_PROFILE is set, or if the boto_profile property above is set.
#
# Supplying AWS credentials here is not recommended, as it introduces
# non-trivial security concerns. When going down this route, please make sure
# to set access permissions for this file correctly, e.g. handle it the same
# way as you would a private SSH key.
#
# Unlike the boto and AWS configure files, this section does not support
# profiles.
#
aws_access_key_id = AXXXXXXXXXXXXXX
aws_secret_access_key = XXXXXXXXXXXXXXXXXXX

Test

Run to check your available hosts.

ansible all --list-hosts

Ping your instances through tags which running on your AWS Account.

ansible tag_Name_<tag_name> -m ping
# ansible tag_Name_testing_os -m ping

Instructions

Ansible configuration file location: /etc/ansible/ansible.cfg

Static Inventory file location: inventory=/etc/ansible/hosts

Dynamic Inventory file location: inventory=/etc/ansible/ec2.py

EC2 keypair location in ansible.cfg. so transfer your keypair at the same location: private_key_file=/etc/keys/<keypair-name>.pem

For transferring the keypair into controller node, use winscp software when you are working on Windows as local system and you’re using in linux, you can use scp command.

After transferring keypair into controller node, you have to change the permission of key, otherwise you can face some permission issuse to access the managed node.

chmod 400 <keypair-name>.pem

Contributing

Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

Please make sure to update tests as appropriate.

License

MIT

Connect with Me.

If you’re facing any issue in this setup, you can reach me out through the following handles