# Ansible Autoscaling with Tower and AWS blog post, instances are NOT authorized by server

**URL:** <https://forum.ansible.com/t/ansible-autoscaling-with-tower-and-aws-blog-post-instances-are-not-authorized-by-server/21336>\
**Category:** Ansible Project\
**Tags:** aws\
**Created:** [May 3, 2016, 2:36am UTC](https://forum.ansible.com/t/ansible-autoscaling-with-tower-and-aws-blog-post-instances-are-not-authorized-by-server/21336 "2016-05-03T02:36:33Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ecoutin\_boingo](https://avatars.discourse-cdn.com/v4/letter/e/ac91a4/32.png) [@ecoutin\_boingo](https://forum.ansible.com/u/ecoutin_boingo)\
**Post date:** [May 3, 2016, 2:36am UTC](https://forum.ansible.com/t/ansible-autoscaling-with-tower-and-aws-blog-post-instances-are-not-authorized-by-server/21336/1 "2016-05-03T02:36:33Z")

</div>

Hello,

So I followed this post:

[https://www.ansible.com/blog/autoscaling-infrastructures](https://www.ansible.com/blog/autoscaling-infrastructures)

And managed to deploy the infrastructure, the problem is the callback isn’t working. I keep getting no available hosts:

curl -k -s -i --data host\_config\_key=mykey\_here https://My\_server\_here/api/v1/job\_templates/759/callback/

HTTP/1.1 400 BAD REQUEST

Server: Apache/2.4.6 (Red Hat Enterprise Linux) OpenSSL/1.0.1e-fips mod\_wsgi/3.4 Python/2.7.5

Vary: Accept,Cookie

Allow: GET, POST, HEAD, OPTIONS

X-API-Time: 0.037s

Content-Length: 43

Connection: close

Content-Type: application/json

{“msg”: “No matching host could be found!”}

Instructions to set inventory are here:

[https://github.com/jsmartin/ansible-tower-ec2/blob/master/README.md](https://github.com/jsmartin/ansible-tower-ec2/blob/master/README.md)

---

<div class="post-metadata">

**Author:** ![sivel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/sivel/32/1198_2.png) [@sivel](https://forum.ansible.com/u/sivel)\
**Post date:** [May 3, 2016, 2:39am UTC](https://forum.ansible.com/t/ansible-autoscaling-with-tower-and-aws-blog-post-instances-are-not-authorized-by-server/21336/2 "2016-05-03T02:39:00Z")

</div>

For tower questions, please contact [support@ansible.com](mailto:support@ansible.com) or use [https://support.ansible.com](https://support.ansible.com)

This list is for the open source Ansible project.

---

<div class="post-metadata">

**Author:** ![ecoutin\_boingo](https://avatars.discourse-cdn.com/v4/letter/e/ac91a4/32.png) [@ecoutin\_boingo](https://forum.ansible.com/u/ecoutin_boingo)\
**Post date:** [May 3, 2016, 3:19am UTC](https://forum.ansible.com/t/ansible-autoscaling-with-tower-and-aws-blog-post-instances-are-not-authorized-by-server/21336/3 "2016-05-03T03:19:11Z")

</div>

I noticed that I was parsing my instances in a public subnet, I even modified the playbook to add a public Ip at the LC level and configured my subnet to be Public. So when the playbook runs the instance is actually public so the Callback doesn’t return anything. The instances should be private so the Inventory can work correctly.