aworldofcode

I updated the API and now everything seems to work, Do we want to upstream the changes in the api ? I am not sure what the process is to...

Also when using the workaround and when executing a task, it just stalls, I suspect because it is not considering the vars like ansible_aws_ssm_bucket_name

I noticed that and updated the collection but still same issue ``` ansible-galaxy collection list amazon.aws # ~/Library/Python/3.9/lib/python/site-packages/ansible_collections Collection Version ---------- ------- amazon.aws 5.2.0 # ~/gitlab/ansible-cda-tools/collections/ansible_collections Collection Version ---------- -------...

@tremble There are no more logs after ``` bash ESTABLISH SSM CONNECTION TO: i-xxxxxx ssm_retry: attempt: 1, caught exception(An error occurred (TargetNotConnected) when calling the StartSession operation: i-xxxxxxxxx is not...

@tremble The target is fully configured. The way I test it is to run from cli the aws ssm start-session comand with --profile option and it immediately responds correctly as...

Let me try again

Here is the update ``` bash ansible-playbook [core 2.14.2] config file = ~/gitlab/ansible-cda-tools/ansible.cfg configured module search path = ['~/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules'] ansible python module location = ~/Library/Python/3.9/lib/python/site-packages/ansible ansible collection location =...

How is this possible ? ``` bash ansible-galaxy collection list amazon.aws # ~/gitlab/ansible-cda-tools/collections/ansible_collections Collection Version ---------- ------- amazon.aws 5.2.0 ``` This is the only collection present on my system

ah ! good catch ``` bash ansible-galaxy collection list community.aws # ~/Library/Python/3.9/lib/python/site-packages/ansible_collections Collection Version ------------- ------- community.aws 5.2.0 # ~/gitlab/ansible-cda-tools/collections/ansible_collections Collection Version ------------- ------- community.aws 5.2.0 echo $AWS_PROFILE $ ```...

so we are moving forward but then it seems to stall ``` bash C02YL0VEJGH8:ansible-cda-tools palea009$ clear ; ansible-playbook PlayBooks/ansible_ssm_connection/ssm_connection_playbook.yml -i inventory/aws_ec2.yaml^C-vvvv C02YL0VEJGH8:ansible-cda-tools palea009$ echo $OBJC_DISABLE_INITIALIZE_FORK_SAFETY C02YL0VEJGH8:ansible-cda-tools palea009$ clear C02YL0VEJGH8:ansible-cda-tools palea009$...