Install Ansible and verify the version to ensure that the target server has SSH access and Python; 2. Create an inventory.ini file to define server groupings; 3. Write a YAML playbook automation configuration such as installing Apache, starting services and deploying pages; 4. Follow best practices to improve maintainability using become, variables, dry-run tests and roles, and use playbook to force security policies such as disabling root login - from then on to achieve consistent, reusable, and version-controllable server management.

Automating Linux server configuration with Ansible is one of the most efficient ways to manage infrastructure—especially when you're dealing with multiple servers or need consistency, repeatable settings. Instead of manually SSH-ing into each machine and running commands, Ansible lets you define your desired state in code (called "playbooks") and apply it across many systems at once.

Here's how to get started and what matters most:

? 1. Set Up Your Control Node

Ansible runs from a "control node" (usually your laptop or a dedicated management server). Install Ansible:

 # On Ubuntu/Debian
sudo apt update && sudo apt install ansible -y

# On RHEL/CentOS/Rocky
sudo dnf install ansible -y

Verify:

 ansible --version

No agents needed on target servers—just SSH access and Python (most modern Linux distros have it).

? 2. Define Your Inventory

Create an inventory file ( inventory.ini ) listing your servers:

 [webservers]
web01 ansible_host=192.168.1.10
web02 ansible_host=192.168.1.11

[dbservers]
db01 ansible_host=192.168.1.20

You can also use groups for logical organization (like webservers , prod , staging )—this makes playbooks reusable.

? 3. Write a Playbook for Common Tasks

A playbook is YAML that describes what to configure. For example, here's a simple one to set up a basic web server:

 ---
- name: Configure Web Server
  hosts: webservers
  becomes: yes # Run as root
  tasks:
    - name: Update package cache
      apt:
        update_cache: yes
      when: ansible_facts.os_family == "Debian"

    - name: Install Apache
      package:
        name: apache2
        state: present

    - name: Start and enable Apache
      systemd:
        name: apache2
        enabled: yes
        state: started

    - name: Copy custom index.html
      copy:
        content: "<h1>Hello from Ansible!</h1>"
        dest: /var/www/html/index.html

This ensures every web server gets Apache installed, started, and has a basic homepage—no manual work required.

? 4. Use Best Practices

• Use become: yes for tasks needing root privileges—but limit it to only what needs it.
• Leverage variables ( vars: or host_vars/ folder) to customize per-server settings (like IP, domain names).
• Test playbooks first with --check (dry-run) and --diff to see what would change:

   ansible-playbook -i inventory.ini site.yml --check --diff

• Use roles for complex setups (eg, a role for Nginx, another for MySQL). Roles keep playbooks clean and reusable.

? Pro Tip: Automate Security & Updates

Ansible isn't just for installing software—it's perfect for enforcing security:

• Automatically disable root SSH login
• Set up UFW/firewalld rules
• Rotate SSH keys
• Install unattended-upgrades

Example task:

 - name: Disable root SSH login
  lineinfile:
    path: /etc/ssh/sshd_config
    regexp: '^PermitRootLogin'
    line: PermitRootLogin no
  notify: restart ssh

Basically, once you write the playbook, applying it is just:

 ansible-playbook -i inventory.ini site.yml

That's it. No more "works on my machine" issues—just consistent, documented, and version-controlled server setups.
Start small (like user management or package installs), then scale to full-stack deployments.

The above is the detailed content of Using Ansible to Automate Linux Server Configuration. For more information, please follow other related articles on the PHP Chinese website!