ELB后端多EC2实例代码同步咨询：单次手动触发替代方案

Got it, let's solve this—you're tired of SSHing into every EC2 instance behind your ELB to run git pull origin master, and you want a single manual trigger to sync all of them at once. Here are three practical, non-scheduled, non-S3-sync solutions that fit your needs:

1. AWS Systems Manager Run Command (AWS Native, No Extra Tools) #

This is my go-to for AWS environments because it's built-in and requires zero additional agents (as long as your instances have the SSM Agent installed, which is default on Amazon Linux 2/2023, RHEL, and Ubuntu LTS).

• Setup steps:
  • Ensure all your ELB backend instances have a consistent tag (e.g., Environment=Production, Role=ELB-Backend)—this makes targeting them easy.
  • Head to the AWS Console → Systems Manager → Run Command.
  • Select the AWS-RunShellScript document from the list.
  • In the "Commands" field, paste your git pull command (adjust the repo path as needed):

    cd /var/www/your-app-repo && git pull origin master
    

    Pro tip: Add error handling if you want, like git fetch && git merge origin master or checking for uncommitted changes first.
  • Under "Targets", select "Specify tags" and enter the tag key/value you assigned to your instances—this will auto-select all matching EC2s.
  • Click "Run" and you'll get real-time execution status for each instance, plus logs if any fail.

2. Parallel SSH (pssh) for Command-Line Fans #

If you prefer working locally with the command line, pssh (Parallel SSH) lets you run commands across multiple hosts in parallel with a single trigger.

• Setup steps:
  • Install pssh on your local machine:
    • macOS: brew install pssh
    • Ubuntu/Debian: sudo apt install pssh
    • RHEL/CentOS: sudo yum install pssh
  • Create a text file (e.g., ec2-backends.txt) with the public IPs or DNS names of your ELB instances, one per line:

    ec2-1-2-3-4.us-east-1.compute.amazonaws.com
    ec2-5-6-7-8.us-east-1.compute.amazonaws.com
    

  • Configure SSH key-based authentication so you don't have to enter passwords for each instance (add your local SSH public key to ~/.ssh/authorized_keys on every EC2).
  • Run the sync command:

    pssh -h ec2-backends.txt -l your-ssh-username -i "cd /path/to/repo && git pull origin master"
    

    • -h: Points to your host list file
    • -l: Your SSH username on the EC2 instances
    • -i: Shows output from each instance in real time

3. Ansible Playbook (For More Complex Workflows) #

If you need to do more than just a git pull (like restarting services, clearing caches, or checking dependencies), Ansible is perfect. It's a configuration management tool that you can trigger manually whenever you need.

• Setup steps:
  • Install Ansible locally: pip install ansible or use your package manager.
  • Create an inventory file (e.g., hosts.ini) with your ELB backend instances grouped together:

    [elb_backends]
    ec2-1-2-3-4.us-east-1.compute.amazonaws.com
    ec2-5-6-7-8.us-east-1.compute.amazonaws.com
    

    Bonus: Use AWS dynamic inventory to auto-discover ELB backend instances instead of maintaining this list manually.
  • Write a simple playbook (e.g., sync-code.yml):

    - name: Sync latest Git code to ELB backend instances
      hosts: elb_backends
      become: true # Use this if you need sudo permissions for your app
      tasks:
        - name: Pull latest master branch
          git:
            repo: 'git@github.com:your-username/your-repo.git'
            dest: /path/to/your/repo
            version: master
            update: yes
        # Optional: Add a task to restart your app service
        - name: Restart application service
          systemd:
            name: your-app-service
            state: restarted
    

  • Trigger the playbook manually whenever you need to sync:

    ansible-playbook sync-code.yml
    

Key Notes for All Solutions #

• Make sure every EC2 instance has Git installed and has permission to pull from your repo (use SSH keys for private repos, or HTTPS credentials if needed).
• Test the command on one instance first before running it across all to catch any issues (like uncommitted local changes that would block the pull).
• For private repos, you can store the SSH key in AWS Secrets Manager (for Systems Manager) or use an Ansible vault (for Ansible) to avoid hardcoding credentials.

内容的提问来源于stack exchange，提问作者Maverick1604