# Timeouts using AWS modules

**URL:** <https://forum.ansible.com/t/timeouts-using-aws-modules/28446>\
**Category:** Ansible Project\
**Tags:** aws\
**Created:** [August 28, 2018, 2:30pm UTC](https://forum.ansible.com/t/timeouts-using-aws-modules/28446 "2018-08-28T14:30:56Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Karl\_Auer](https://avatars.discourse-cdn.com/v4/letter/k/cc9497/32.png) [@Karl\_Auer](https://forum.ansible.com/u/Karl_Auer)\
**Post date:** [August 28, 2018, 2:30pm UTC](https://forum.ansible.com/t/timeouts-using-aws-modules/28446/1 "2018-08-28T14:30:56Z")

</div>

I am getting a LOT of read timeouts working with AWS modules. The commonest is with ec2\_group, but I’ve seen it with elb\_application\_lb and a couple of others as well. Sometimes running the playbook again gets past it, sometimes not. With biggish playbooks it is getting to be real problem.

Is this something I can do anything about?

Regards, K.

Sample (sorry about the formatting):

TASK [sg : Create a security group ADFS-wap-sg protecting WAP instances] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: ssl.SSLError: (‘The read operation timed out’,)  
fatal: [localhost]: FAILED! =\> {“changed”: false, “module\_stderr”: “Traceback (most recent call last):\n File "/tmp/ansible\_NEDa9I/ansible\_module\_ec2\_group.py", line 1021, in \n main()\n File "/tmp/ansible\_NEDa9I/ansible\_module\_ec2\_group.py", line 890, in main\n group, groups = group\_exists(client, module, vpc\_id, group\_id, name)\n File "/tmp/ansible\_NEDa9I/ansible\_module\_ec2\_group.py", line 831, in group\_exists\n all\_groups = get\_security\_groups\_with\_backoff(client).get(‘SecurityGroups’, )\n File "/tmp/ansible\_NEDa9I/ansible\_modlib.zip/ansible/module\_utils/cloud.py", line 153, in retry\_func\nssl.SSLError: (‘The read operation timed out’,)\n”, “module\_stdout”: “”, “msg”: “MODULE FAILURE”, “rc”: 1}

---

<div class="post-metadata">

**Author:** ![Pshem\_Kowalczyk](https://avatars.discourse-cdn.com/v4/letter/p/e480ec/32.png) [@Pshem\_Kowalczyk](https://forum.ansible.com/u/Pshem_Kowalczyk)\
**Post date:** [August 29, 2018, 4:44am UTC](https://forum.ansible.com/t/timeouts-using-aws-modules/28446/2 "2018-08-29T04:44:30Z")

</div>

This generally indicates connectivity problems. Are you behind a proxy of some sort (might be transparent). I have seen those sort of issues in various corporate environments that used proxies to inspect all traffic.

kind regards  
Pshem

---

<div class="post-metadata">

**Author:** ![Karl\_Auer](https://avatars.discourse-cdn.com/v4/letter/k/cc9497/32.png) [@Karl\_Auer](https://forum.ansible.com/u/Karl_Auer)\
**Post date:** [August 29, 2018, 4:50am UTC](https://forum.ansible.com/t/timeouts-using-aws-modules/28446/3 "2018-08-29T04:50:07Z")

</div>

Nope, it’s not a connectivity, or not that sort of connectivity issue. It’s been getting worse with each version of Ansible, though that is correlation, not necessarily causation 🙂

Everything I do is on localhost, running ansible AWS modules, which talk to AWS rather than to actual hosts. I find it a bit suspicious that the lion’s share of the issues are with security groups, but I’m not sure what I’m suspicious of 🙂

Regards, K.