# Ansible 1.9.4,  AWS Auto scaling "Launching a new EC2 instance. Status Reason: The parameter SecurityGroup is not recognized. "

**URL:** <https://forum.ansible.com/t/ansible-1-9-4-aws-auto-scaling-launching-a-new-ec2-instance-status-reason-the-parameter-securitygroup-is-not-recognized/19775>\
**Category:** Ansible Project\
**Tags:** aws\
**Created:** [November 16, 2015, 3:44pm UTC](https://forum.ansible.com/t/ansible-1-9-4-aws-auto-scaling-launching-a-new-ec2-instance-status-reason-the-parameter-securitygroup-is-not-recognized/19775 "2015-11-16T15:44:46Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Adrian\_Black1](https://avatars.discourse-cdn.com/v4/letter/a/b5a626/32.png) [@Adrian\_Black1](https://forum.ansible.com/u/Adrian_Black1)\
**Post date:** [November 16, 2015, 3:44pm UTC](https://forum.ansible.com/t/ansible-1-9-4-aws-auto-scaling-launching-a-new-ec2-instance-status-reason-the-parameter-securitygroup-is-not-recognized/19775/1 "2015-11-16T15:44:46Z")

</div>

Im trying to do an auto scaling group in AWS

Below is my script.

It runs and almost completes (it sets up lb, asg and lc in AWS) but times out with

“msg: Waited too long for new instances to become viable. Mon Nov 16 15:35:31 2015”

Under AWS “Activity History” on Auto Scaling Group i get

“Launching a new EC2 instance. Status Reason: The parameter SecurityGroup is not recognized. Launching EC2 instance failed.”

I have tried looking for that message with only 2 hits in all of google so its not a common error.

Anything im doing wrong in the below or any idea about the message?

Thanks

---

<div class="post-metadata">

**Author:** ![Adrian\_Black1](https://avatars.discourse-cdn.com/v4/letter/a/b5a626/32.png) [@Adrian\_Black1](https://forum.ansible.com/u/Adrian_Black1)\
**Post date:** [November 16, 2015, 5:35pm UTC](https://forum.ansible.com/t/ansible-1-9-4-aws-auto-scaling-launching-a-new-ec2-instance-status-reason-the-parameter-securitygroup-is-not-recognized/19775/2 "2015-11-16T17:35:36Z")

</div>

I think the issue was

security\_groups: [‘http/https’] on ec2\_lc

Changed to use ids though doco isnt very clear on this in either wording “A list of security groups into which instances should be found” or example [‘group1’, ‘group2’]  
[http://docs.ansible.com/ansible/ec2\_lc\_module.html](http://docs.ansible.com/ansible/ec2_lc_module.html)