# AWS elastic load balancer rules

**URL:** <https://forum.ansible.com/t/aws-elastic-load-balancer-rules/30170>\
**Category:** Ansible Project\
**Tags:** aws\
**Created:** [April 23, 2019, 2:30pm UTC](https://forum.ansible.com/t/aws-elastic-load-balancer-rules/30170 "2019-04-23T14:30:17Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Adam](https://avatars.discourse-cdn.com/v4/letter/a/4af34b/32.png) [@Adam](https://forum.ansible.com/u/Adam)\
**Post date:** [April 23, 2019, 2:30pm UTC](https://forum.ansible.com/t/aws-elastic-load-balancer-rules/30170/1 "2019-04-23T14:30:17Z")

</div>

Hi -

As far as I can tell, it’s not possible to configure AWS application load balancer rules for attributes like HTTP headers via Ansible. Is that correct? If not, does anyone know any examples of how to do this?

If it doesn’t exist yet, does anyone know if someone is already working on adding this feature?

Thanks in advance,  
Adam

---

<div class="post-metadata">

**Author:** ![Dick\_Visser](https://avatars.discourse-cdn.com/v4/letter/d/d9b06d/32.png) [@Dick\_Visser](https://forum.ansible.com/u/Dick_Visser)\
**Post date:** [April 23, 2019, 5:00pm UTC](https://forum.ansible.com/t/aws-elastic-load-balancer-rules/30170/2 "2019-04-23T17:00:51Z")

</div>

My default approach for (so far) unsupported features is to resort to command tasks, running the AWS cli.

For idempotency I usually have two tasks, one to check the current configuration, and one to make any changes (if needed, based on the results of the first task).

Dick