# ec2\_vol potential PR - could use some input (aws, boto, ec2\_vol)

**URL:** <https://forum.ansible.com/t/ec2-vol-potential-pr-could-use-some-input-aws-boto-ec2-vol/23950>\
**Category:** Ansible Developer\
**Tags:** aws\
**Created:** [March 13, 2017, 12:18pm UTC](https://forum.ansible.com/t/ec2-vol-potential-pr-could-use-some-input-aws-boto-ec2-vol/23950 "2017-03-13T12:18:06Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Matthew\_Coltman](https://avatars.discourse-cdn.com/v4/letter/m/58f4c7/32.png) [@Matthew\_Coltman](https://forum.ansible.com/u/Matthew_Coltman)\
**Post date:** [March 13, 2017, 12:18pm UTC](https://forum.ansible.com/t/ec2-vol-potential-pr-could-use-some-input-aws-boto-ec2-vol/23950/1 "2017-03-13T12:18:06Z")

</div>

(re-posting to the correct list this time 🙂 )

Hey all,

This is my first time attempting to contribute here and I’m mainly after a bit of a sanity check.

This is the issue I’m looking at: [https://github.com/ansible/ansible/issues/21588](https://github.com/ansible/ansible/issues/21588)

The module currently uses boto but boto3 is needed to modify volumes. I think the best way to handle this would be to just convert the whole module to use boto3. Of course this can break the module for users missing boto3, but this is an easy fix and boto has been deprecated for a some time now. So I know what I’d do but I’m more wondering if this fits in with the “Ansible way” of doing things.

If I go with this then some integration tests also seem like a good idea as there are none currently.

I think that’s it for now, any help appreciated. Cheers!

---

<div class="post-metadata">

**Author:** ![Matthew\_Coltman](https://avatars.discourse-cdn.com/v4/letter/m/58f4c7/32.png) [@Matthew\_Coltman](https://forum.ansible.com/u/Matthew_Coltman)\
**Post date:** [March 14, 2017, 1:56pm UTC](https://forum.ansible.com/t/ec2-vol-potential-pr-could-use-some-input-aws-boto-ec2-vol/23950/2 "2017-03-14T13:56:23Z")

</div>

Another option is to use both modules side by side, but then even if we handle things nicely users without boto3 will miss out on new functionality:

[https://aws.amazon.com/blogs/developer/migrating-to-boto3/](https://aws.amazon.com/blogs/developer/migrating-to-boto3/)

Plus just handling these cases in the first place adds complexity.
