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
Labels:

Comments

Post a Comment

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. ...
Post a Comment
Read more

Common Jenkins Errors and How to Fix Them

As you work with Jenkins, you might run into a variety of issues. Here's a rundown of some of the most common problems and how to resolve them: 1. Permission Issues: 😣 Error: Jenkins can't access files. ✅ Solution: Ensure Jenkins has the appropriate permissions or run it as the correct user. 2. Build Failures: 😡 Error: Builds are failing. ✅ Solution: Review the logs, and address issues such as missing dependencies or incorrect configurations. 3. Workspace Cleanup Problems: 🚫 Error: Workspace becomes cluttered. ✅ Solution: Configure Jenkins to automatically clean up after each build to prevent unnecessary file accumulation. 4. Plugin Compatibility Issues: 😬 Error: Plugins are not working with Jenkins. ✅ Solution: Make sure your plugins a...
Post a Comment
Read more

What is Linux?

Linux is an Open-Source Operating System based on Unix.  Linux was first introduced by Linus Torvalds.  The main purpose of Linux was to provide free and low-cost Operating System for users. Since Linux is cost-free, so it is conveniently downloadable and used by people.  Linux is open-source, so it is open to use, and developers may also try to improve the Linux operating system’s features.  It’s a multi-use operating system so multiple people may use the model.  Linux can operate on various types of hardware, so Linux is transportable.  Linux is secure, as it offers secure passwords and data encryption.
Post a Comment
Read more