Playbooks have been created to deploy below
a. New EC2 instance
b. New S3 Bucket with a a group policy
c. New RDS instance and RDS database for MySQL
d. All setup related to Appstore deployment and appstore deployment itself

Issues Identified
Playbook creates a new EC2 instance even if one with similar names exist already.
Timeout during the [wait for EC2 to start] results in the Playbooks stopping during execution
Python interpreter check during ansible executions

New feature
Ability to pass the argument of the instance name inline with ansible-playbook command rather than from group_vars/all.yml

Ec2 check has been implemented
The timeout of connection break is improved

for using python3 ansible install using
pip3 install ansible

for passing arguments via command line use the below command
ansible-playbook main.yml --extra-vars "ec2_name=DEV-AppStore123"

I would like to use python2 instead of python3 due to easy of installation and update. Is okay Chester Dias

that will work for now....but going forward it can throw issues because some modules of ansible need python 3 to work as expected.

OK. I was never able to ansible-playbook to run under python3 on my test control node. Without a repeatable process to use ansible-playbook under python3 then I think we need to stick with python3. If there is not need to use python3 right this minute, I am fine with using python2 for now.

Next request:

Could you modify the playbooks so that the control node creates a security group it can use to connect to the target app store EC2's it creates?
It should make such a security group just once and then re-use it as required.

will get started

Next request:

Could you modify the playbooks so that the control node creates a security group it can use to connect to the target app store EC2's it creates?
It should make such a security group just once and then re-use it as required.

The above request is completed

I am moving this to "complete" as the first draft has been created. Further improvements and bug fixes will be captured in new Jira issues.