Dave Seff
Dave Seff
@PeterHiggins had explained this to me recently ( we work together ). Because our company insists on defining egress rules for our SGs, We have to account for S3 enpoints....
I had the same issue. Error message below. Strangely, All my work is being don in us-west-1. Don't know why it's complaining about us-east-1: Error: Could not run: Puppet detected...
Also, It seems that if this is put into a puppet manifest, it will complain everytime, whereas if just run via 'puppey apply' all is good for a onetime run:...
A workaround is to add instance_initiated_shutdown_behavior => 'terminate' This works, but it would seem that this would be a required parameter, not an optional one.
This AMI happens to be a generic ubuntu 14.04 image from amazon. I suspect this error is coming from the aws ruby sdk and not this puppet module. I'm just...
+1 - Also with the abilit to specify an elb name to alias to
I added this recently in my own branch. I may be able to do a quick PR
I just ran into this issue as well.
Is this something that can be fixed within this module, or an issue that is inherently within puppet? I'm having a rough time convincing my company to use puppet to...
This may have been taken care of with my PR #505 I had to remove the explicit requirement for the gateway in order to accommodate the peering connections.