Skip to main content

Steps to Set Up Ansible on AWS EC2 Instances

Ansible Setup on AWS

Ansible Setup on AWS

Step 1: Launch Instances

Launch Amazon Linux instances on AWS:

  • Control Node: The server to install Ansible.
  • Managed Nodes: Servers managed by Ansible.

Step 2: Install Ansible on the Control Node

Update the system:

sudo yum update -y

Install EPEL Repository:

sudo amazon-linux-extras install epel -y

Install Ansible:

sudo yum install ansible -y

Step 3: Create a User on All Servers

Create a user, for example, ansibleuser:

sudo useradd ansibleuser
sudo passwd ansibleuser

Step 4: Grant Sudo Permission to the User

Edit the sudoers file:

sudo visudo

Add this line:

ansibleuser ALL=(ALL) NOPASSWD: ALL

Step 5: Setup Passwordless Authentication on All Servers

Edit SSH configuration:

sudo vim /etc/ssh/sshd_config

Set PasswordAuthentication to yes and restart SSH:

sudo service sshd restart

Generate SSH Key on Control Node:

ssh-keygen -t rsa

Copy the SSH Key to Managed Nodes:

ssh-copy-id ansibleuser@<managed_node_ip>

Step 6: Uncomment Hosts Entry in Ansible Configuration

Edit the Ansible config file:

sudo vim /etc/ansible/ansible.cfg

Uncomment the line:

inventory = /etc/ansible/hosts

Step 7: Configure the Hosts File

Edit the hosts file and add Managed Nodes:

[web-server]
managed_node1_pvt_ip
managed_node2_pvt_ip

[db-server]
managed_node3_pvt_ip
managed_node4_pvt_ip

Step 8: Run Ad-hoc Commands

Test connectivity with:

ansible all -m ping

Step 9: Common Ad-hoc Commands

List all hosts:

ansible all --list-hosts

Ping all hosts:

ansible all -m ping

Note:

To avoid receiving a warning, add the line interpreter_python=auto_silent to the file /etc/ansible/ansible.cfg at any location.

Run the uptime command:

ansible all -m command -a "uptime"

Step 10: Ansible Playbook

A Playbook is a YAML configuration file that defines tasks for remote servers. Run a Playbook with:

ansible-playbook <playbook_name>.yaml

Step 11: Ansible Playbook Commands

Check for syntax errors:

ansible-playbook <playbook_name>.yaml --syntax-check

Perform a dry run:

ansible-playbook <playbook_name>.yaml --check

Comments

Popular posts from this blog

A Complete CI/CD Pipeline

Complete CI/CD Pipeline Using GitHub, Jenkins, Maven, SonarQube, Nexus, and Docker A well-designed CI/CD pipeline plays a critical role in modern DevOps practices by automating software delivery, improving code quality, and reducing deployment risks. In this article, I will explain how I build an automated CI/CD pipeline using GitHub, Jenkins, Maven, SonarQube, Nexus Repository, Docker, and Docker Hub. Source Code Management with GitHub The CI/CD workflow begins with storing the application source code in GitHub. Developers regularly push code changes or create pull requests to collaborate on features and bug fixes. Whenever new code is pushed to the repository, GitHub triggers Jenkins automatically through a webhook. This integration helps start the CI/CD pipeline without manual intervention. Code Checkout Stage in Jenkins The first stage of the pipeline is the checkout process. Jenkins connects to the GitHub repository and pulls the latest version of the source code. ...

Terraform for AWS: Step-by-Step Infrastructure Automation That Actually Works

How I Use Terraform to Provision and Manage AWS Infrastructure Efficiently Infrastructure as Code (IaC) has become a critical part of modern cloud operations, and Terraform is one of the most popular tools for automating cloud infrastructure deployment. In this article, I'll share how I use Terraform to build and manage AWS resources such as Virtual Private Clouds (VPCs), EC2 instances, Application Load Balancers (ALBs), and Auto Scaling Groups. Building AWS Infrastructure with Terraform My infrastructure deployment process begins by defining all AWS resources as code. This approach ensures consistency, repeatability, and easier management across multiple environments. The first step is creating a secure network architecture using a VPC. Within the VPC, I configure public and private subnets, route tables, internet gateways, and other networking components required for application deployment. Once the networking layer is ready, I deploy EC2 instances inside private su...

Master Linux Administration for DevOps: Powerful Commands, Troubleshooting Tips & Best Practices

Linux administration is one of the most important skills for anyone working in DevOps. From application servers and CI/CD platforms to containers and cloud infrastructure, Linux-based systems are widely used in modern technology environments. In my day-to-day DevOps activities, I regularly work with Linux commands to manage files, monitor processes, troubleshoot services, investigate network problems, analyze logs, and resolve production issues. This guide covers essential Linux administration concepts and commands that are useful for DevOps engineers, along with practical examples of how they can be applied during everyday troubleshooting. 1. Understanding Linux File Permissions Linux uses a permission system to control access to files and directories. The three basic permissions are: Read (r) – Allows a user to view the contents of a file or directory. Write (w) – Allows modifications to a file or directory. Execute (x) – Allows a file to be executed or a director...