Using the security group parameter does not work about amazon-ecs-cli HOT 8 CLOSED

Thanks for your comment @perryn , it motivated me to look into why the the security group wasn't showing up in the drop down when trying to enable access to an rds instance. After looking a little deeper, I figured out how to get it to work!

The issue we're seeing is caused by trying to assign a security group to a VPC it doesn't belong to. The default 'ecs-cli up' call will create a new VPC which can't access the security group you specify. To get this to work, add the --vpc and --subnets arguments for the vpc that owns the security group you're trying to use.

Enjoy! 💃

from amazon-ecs-cli.

I can reproduce this error. In addition to the error described above by @mehmeta, if one looks at the autoscaling interface, one can see a bunch of instances failed to start with the error:

The parameter SecurityGroup is not recognized

from amazon-ecs-cli.

Have the same issue

from amazon-ecs-cli.

We hit this too. Pretty bad that one of the documented parameters doesn't work at all.

from amazon-ecs-cli.

Same here and it's the only way I can find to create an ECS cluster with more than one port open - which is pretty vital for anything other than a trivial web app.

from amazon-ecs-cli.

Did any of you solve this yet? I'm seeing the same issue. I also noticed that I can't add an inbound rule for an RDS security group for the security group created by ecs up.

from amazon-ecs-cli.

@jestrada We dealt with it by allowing ecs-cli to create its own security group and then modifying that to match our requirements (although it sounds like you already tried that)

from amazon-ecs-cli.

@jestrada
Thanks a ton... Finally it worked for me..... 👍

from amazon-ecs-cli.