# Alternatives to exporting environment variables

**URL:** <https://forum.ansible.com/t/alternatives-to-exporting-environment-variables/23253>\
**Category:** Ansible Project\
**Tags:** aws\
**Created:** [December 14, 2016, 12:20pm UTC](https://forum.ansible.com/t/alternatives-to-exporting-environment-variables/23253 "2016-12-14T12:20:32Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Chethan\_ARAVIND\_T\_S](https://avatars.discourse-cdn.com/v4/letter/c/5e9695/32.png) [@Chethan\_ARAVIND\_T\_S](https://forum.ansible.com/u/Chethan_ARAVIND_T_S)\
**Post date:** [December 14, 2016, 12:20pm UTC](https://forum.ansible.com/t/alternatives-to-exporting-environment-variables/23253/1 "2016-12-14T12:20:32Z")

</div>

Hi,  
I have attached a playbook to export environment variables for proxy and aws keys. Even if I run this or include this at the top of provisioning script, I am getting an error “NO HANDLER WAS READY TO AUTHENTICATE”. But if I run those commands on terminal before running the provisioning script, I am able to get the job done. I don’t want to run the commands manually, Is there an efficient way of running those commands from playbook itself?

this is the playbook I wrote to export the environment variables

---

<div class="post-metadata">

**Author:** ![oravirt](https://avatars.discourse-cdn.com/v4/letter/o/3e96dc/32.png) [@oravirt](https://forum.ansible.com/u/oravirt)\
**Post date:** [December 15, 2016, 7:17pm UTC](https://forum.ansible.com/t/alternatives-to-exporting-environment-variables/23253/2 "2016-12-15T19:17:01Z")

</div>

Hi,

Take a look at this: [http://docs.ansible.com/ansible/playbooks\_environment.html](http://docs.ansible.com/ansible/playbooks_environment.html)

regards  
/Micke