# Ansible AWS "Cloud-Control" Modules: Clarification

**URL:** <https://forum.ansible.com/t/ansible-aws-cloud-control-modules-clarification/21937>\
**Category:** Ansible Project\
**Tags:** aws\
**Created:** [July 6, 2016, 5:06pm UTC](https://forum.ansible.com/t/ansible-aws-cloud-control-modules-clarification/21937 "2016-07-06T17:06:43Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Robert\_Glenn](https://avatars.discourse-cdn.com/v4/letter/r/e36b37/32.png) [@Robert\_Glenn](https://forum.ansible.com/u/Robert_Glenn)\
**Post date:** [July 6, 2016, 5:06pm UTC](https://forum.ansible.com/t/ansible-aws-cloud-control-modules-clarification/21937/1 "2016-07-06T17:06:43Z")

</div>

> > Whereas classically ansible will execute tasks in its host loop against multiple remote machines, most cloud-control steps occur on your local machine with reference to the regions to control.

Some of the AWS module documentation are implicit (e.g. [http://docs.ansible.com/ansible/ec2\_module.html](http://docs.ansible.com/ansible/ec2_module.html)) about the above, but none seem to be explicit (many seem to ignore the above completely).

Does “most” here mean “all”?

Can someone clarify which cloud-control modules behave differently?

Can modules requiring special treatment be designated as such in the documentation?

best,

Robert Glenn