Well you can always assign Elastic IPs to your VPC instances, if they are on a single public subnet. (Depending on how you have things configured.)
Also, for a private subnet, you can setup an internet gateway instance that can handle outgoing NAT for you. Other than that, some fancier options are to run a replica of your puppetmaster in a public subnet, or even run a foreman "smart-proxy" puppet proxy in a public VPC subnet, that your other VPC nodes can accces. (Let me know if any of these sound appealing and I can get you more info. Or at least point you in the right direction.) -Brian On Tue, Mar 20, 2012 at 12:03 AM, Denmat <tu2bg...@gmail.com> wrote: > Hi list, > > Quick general question, what's the current best way to deploy to an Amazon > VPC (without VPN to central puppet master)? Deliberately vague to get wide > results :) > > Has anyone got good posts on this? > > TIA > Den > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- <http://aws.amazon.com/solutions/solution-providers/brandorr/> -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
