Get the AWS CLI working first. Can’t help much there - perhaps it is a path issue?
Regards, K.
Yes I am trying that but I am on python 2.7 and facing issue with aws CLI. Even after installation, I am still unable to see that path. Trying for that. Else I need to get another EC2 and perform installation from scratch and see what happens.
Thanks for your help Karl.
Appreciate it
Regards
Amit
This is now a basic user problem “why can’t this program be found”. This is not a problem that we can solve for you.
But once you have the AWS CLI working, you will be in a much better position to figure out why Ansible is not doing what you expect.
Regards, K.
Hi Amit,
can you please try by making become:true in playbook.
Just for checking.
Hi Amit,
Also please make sure your botocore is able to read ~/.aws/configure/.
Ideally when you try dynamic inventory, you should be running your playbook using below.
Aws_profile={profile in config} ansible-playbook {playbook namr} -i {input variable file}
Hi All,
I am able to run AWS command line now.
I was will try to run the playbook now and keep you posted on this.
Regards
Amit
Hi
After this long iteration of support, it would be appreciated if you shared with us the cause of the issue. Also, for everyone else to learn from.
Thx!
Sure once I complete it.
I will share all the details
Thanks everyone
Regards
Amit
Hello All,
First of all thanks all of you for your support.
Sorry for the delay in writing back on to the group but it was busy due to Dorian.
I was able to create the bucket successfully using Ansible.
I have done all the installations again (Ansible, AWS CLI and Boto)
I have tested the AWS CLI which was working fine and then tested bucket creation using Ansible.
Do remember that installation for boto is very important at correct location else that can also be the cause of problem.
Let me know if further details are required.
Regards
Amit