# EC2 module docs are incorrect

**URL:** <https://forum.ansible.com/t/ec2-module-docs-are-incorrect/13432>\
**Category:** Ansible Project\
**Tags:** aws\
**Created:** [September 8, 2013, 2:26pm UTC](https://forum.ansible.com/t/ec2-module-docs-are-incorrect/13432 "2013-09-08T14:26:33Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![John\_Fuller](https://avatars.discourse-cdn.com/v4/letter/j/5f9b8f/32.png) [@John\_Fuller](https://forum.ansible.com/u/John_Fuller)\
**Post date:** [September 8, 2013, 2:26pm UTC](https://forum.ansible.com/t/ec2-module-docs-are-incorrect/13432/1 "2013-09-08T14:26:33Z")

</div>

The docs for the EC2 module mention that you have to set aws\_secret\_key, aws\_access\_key and aws\_url. But in Ansible version 2.3 (pulled from the PPA) both the env variables and the parameters should be ec2\_secret\_key, etc. So, replace aws with ec2.

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan](https://avatars.discourse-cdn.com/v4/letter/m/c4cdca/32.png) [@Michael\_DeHaan](https://forum.ansible.com/u/Michael_DeHaan)\
**Post date:** [September 8, 2013, 3:17pm UTC](https://forum.ansible.com/t/ec2-module-docs-are-incorrect/13432/2 "2013-09-08T15:17:54Z")

</div>

There is no Ansible 2.3 release, I assume you meant 1.3.

Yes, we cleaned up consistency on all of these, keeping the old parameters as aliases for backwards compatibility.

Please file a bug on [github.com/ansible/ansible](http://github.com/ansible/ansible) so we can update the docs, or alternatively, submit a pull request to update the module source (documentation is embedded, see library/cloud in the checkout).

---

<div class="post-metadata">

**Author:** ![John\_Fuller](https://avatars.discourse-cdn.com/v4/letter/j/5f9b8f/32.png) [@John\_Fuller](https://forum.ansible.com/u/John_Fuller)\
**Post date:** [September 12, 2013, 1:02am UTC](https://forum.ansible.com/t/ec2-module-docs-are-incorrect/13432/3 "2013-09-12T01:02:58Z")

</div>

Sorry for the confusion here. I’m using 1.2.3, the latest stable version I believe. Now that I have had a chance to look at 1.3, I see what you are referring to. The docs are correct for 1.3 and the EC2 module checks for both the old parameter and the changed parameters. So, I guess this problem will work itself out since 1.3 is fast approaching release.

Thanks for the heads up, I will switch to 1.3 since it has features that I need.