# EC2 Module ignoring zone parameter

**URL:** <https://forum.ansible.com/t/ec2-module-ignoring-zone-parameter/12703>\
**Category:** Ansible Project\
**Created:** [April 19, 2013, 8:43pm UTC](https://forum.ansible.com/t/ec2-module-ignoring-zone-parameter/12703 "2013-04-19T20:43:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Leonardo\_Murillo](https://avatars.discourse-cdn.com/v4/letter/l/5e9695/32.png) [@Leonardo\_Murillo](https://forum.ansible.com/u/Leonardo_Murillo)\
**Post date:** [April 19, 2013, 8:43pm UTC](https://forum.ansible.com/t/ec2-module-ignoring-zone-parameter/12703/1 "2013-04-19T20:43:36Z")

</div>

This is solved - you need to specify the proper endoint for the zone you’ve specified. In other words, if you specify zone: us-west-1c you need to specify ec2\_url: [https://ec2.us-west-1.amazonaws.com](https://ec2.us-west-1.amazonaws.com)

Otherwise you’ll run into the detailed behavior.

---

<div class="post-metadata">

**Author:** ![Lester\_Wade](https://avatars.discourse-cdn.com/v4/letter/l/97f17d/32.png) [@Lester\_Wade](https://forum.ansible.com/u/Lester_Wade)\
**Post date:** [April 20, 2013, 8:32am UTC](https://forum.ansible.com/t/ec2-module-ignoring-zone-parameter/12703/2 "2013-04-20T08:32:09Z")

</div>

A lot of folks have run foul of this lately. I’ll look to change the connection method this weekend, I think we should move away from the env variables and begin to explicitly declare region and zone. This also ties into some things we discussed about ensuring the aws-related modules are used for consistent deployment of the same infrastructure regardless of the region and zone.