# Boto Version Support in Modules

**URL:** <https://forum.ansible.com/t/boto-version-support-in-modules/20975>\
**Category:** Ansible Developer\
**Tags:** aws\
**Created:** [March 23, 2016, 9:10pm UTC](https://forum.ansible.com/t/boto-version-support-in-modules/20975 "2016-03-23T21:10:41Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Gordon\_Towne](https://avatars.discourse-cdn.com/v4/letter/g/bc8723/32.png) [@Gordon\_Towne](https://forum.ansible.com/u/Gordon_Towne)\
**Post date:** [March 23, 2016, 9:10pm UTC](https://forum.ansible.com/t/boto-version-support-in-modules/20975/1 "2016-03-23T21:10:41Z")

</div>

We’ve implemented a modification to the “ec2\_scaling\_policy” module to fix [this issue](https://github.com/ansible/ansible-modules-core/issues/3130) that we’re now using at work that we’d like to open source. The fix depends on boto3 in a module that previously only requried boto 2.x. Before I open a pull request, I’m wondering if there is any official position on boto version support and backward compatibility in AWS modules. Is the preferred tact roughly “use boto3 only where required and document those places” as described [here](https://groups.google.com/d/msg/ansible-devel/bvkr-9iAWm8/_CMm_PYyEwAJ)? Is there any value in supporting environments where boto3 is installed but not boto 2.x?

I’m new to the project, so forgive me if this is a dumb question but I wasn’t able to find a definitive answer.

Thanks,

Gordon Towne