Rails Rubber AWS EC2 Deployment Issues with Groups and Rules

If you are having trouble getting started with Rubber then this is for you.
This post resolves errors:
SecurityGroupLimitExceeded => You have exceeded the number of VPC security groups allowed per instance
MissingParameter => Source group ID missing.

The issue is that by default Rubber is creating different security groups for each role. You will notice the console printing numerous “Creating Security Group #{x}” lines. The max allowed without petitioning is 5 (http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Appendix_Limits.html) without petitioning.

First run cap rubber:destroy_all.. *Unless you already have production instances. I am assuming this is a fresh first time setup failing.

To force Rubber to use only one security group go into rubber.yml and set…
auto_security_groups: false
isolate_security_groups: false

After that it may work, or you may get error saying security groups exists… Go here to read how to access security groups. Once in the panel delete all security groups but “default”. http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_SecurityGroups.html#DeleteSecurityGroup

If you are getting errors about rules, then select the “default” user group in the AWS panel . This will bring up the rules. Delete all custom TCP rules. After this everything should work. You may need to repeat deleting groups and rules, since Rubber seems to do a terrible job of managing those.

Also read...

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>