*subnets. Yes, that's right. the ec2_vpc module doesn't do NAT related things. you'll have to launch another EC2 instance for that. take a look here: https://github.com/dfederlein/ansible-aws/blob/master/vpc/ec2_vpc.yml it requires having the aws cli tools set up on your local host.
On Monday, 5 January 2015 22:30:37 UTC+1, Gary Malouf wrote: > > Is setting up a NAT supported (but undocumented) or do we need to manually > launch instances(s) via the normal ec2 module to act as a NAT for private > sub-domains? > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/1eafc8a5-b13f-4631-a349-6964a3630bc6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
