Re: [vagrant-up] [Multi-Provider] Hybrid Environment - How to resolve dynamically generated addresses for instances on EC2, Azure, etc. from local VMs?

Hello Joe. If you are using only 1 region in AWS, then you can check consul. One DC will be your office, other DC will be AWS, and you join them over wan. The office will require the box have an ip over the lan. So everyone will be able to ping :) On every vagrant box you can install consul

Re: [vagrant-up] [Multi-Provider] Hybrid Environment - How to resolve dynamically generated addresses for instances on EC2, Azure, etc. from local VMs?

Hi Joe, the vagrant-triggers plugin might be useful in that context too (e.g. lookup the ec2 dynamic ip via `vagrant ssh-config ` and pass that info to a shared state file, where the other VMs can read it): https://github.com/emyl/vagrant-triggers HTH, Torben On Wed, Nov 4, 2015 at 8:04 PM, Joe

[vagrant-up] [Multi-Provider] Hybrid Environment - How to resolve dynamically generated addresses for instances on EC2, Azure, etc. from local VMs?

We've hit the memory limit on our local machines and I am looking into a sustainable way to run a multi-provider development environment in Vagrant where we have 1-3 VMs locally and one node on EC2 (per developer). The problem is not communicating workstation => EC2, but between VMs and EC2.