Running Ansible playbook using AWS Systems Manager | AWS Automation | AWS State Manager

DevOps Online Training Registration form:
For Online training, connect us on WhatsApp at +91-9642858583

============ Online Trainings =========
Online Trainings:
DevOps Practitioner Training ►
Live Realtime Project Training ►
Interview Preparation Sessions ►

============ Udemy Courese =========
AR Shankar Udemy Courses ►
Linux for DevOps ►
Git for DevOps ►
Ansible for DevOps Beginners ►
Maven for DevOps ►
DevOps Project ►

============ Our Other Courses =========
Valaxy Ultimate Plan ►
DevOps AWS and Python ►
DevOps AWS and Shell Scripting ►
All About AWS ►

Other Courses:
DevOps Course ►
Azure Administration ►
Production Ready Project ►
Kuberentes Project ►
AWS (Amazon Web Services) ►
Python Complete Course ►
Shell Scripting ►
AWS automation with Boto3 ►
Valaxy PPTs ►

============ Free resources =========
Free Access to all skillshare courses for 1 month ►
DevOps Resumes ►
Tools to learn in DevOps ►

============ Connect with Us =========
Facebook ►
Instagram ►
LinkedIn ►
Website ►

#DevOps #Valaxy #AWS


6 thoughts on “Running Ansible playbook using AWS Systems Manager | AWS Automation | AWS State Manager”
  1. sir I have found this video very useful but I have 1 doubt . Though you have created one instance & configured SSM on it which is a master server then what about those client servers? how to configure them all will SSM ? Please clear my doubt .

  2. i got one question..Why are we installing ansible on the machine where we execute ansible playbook? Isn't it required only for machines from where we execute playboos..? or maybe it is running on itself as localhost?

  3. Sir, my doubts are 1)why to use ansible as we can use any thing with run command in ssm
    2)is there any specific adoption for run command and ansible paybooks usage, if yes, please share use case for both

  4. Good one. But i have been searching for a real world example where ansible instances are known only through Ansible inventories and not upfront. And the ssm invocation through console or command line expects us to know the target instances upfront to call the playbook that defeats the utility of Ansible playbook inventories itself. Do you have a way to do that?

Leave a Reply

Your email address will not be published.

Captcha loading...