[lxc-users] Networking issues with LXC containers in EC2

[Peter Steele]

I should have added that I have no issue running our software on a 
single EC2 instance with containers running on that instance. We can 
assign multiple IPs to the instance itself, as well as to the containers 
running under the instance, and the containers can all communicate with 
each other as well as with the host. The problem occurs when we have 
more than one EC2 instance and need to have the containers in separate 
instances to communicate with each other. You're right though: If no one 
on this list has actually dealt with this issue themselves, the quickest 
answer is probably to talk to AWS directly.

Thanks.

Peter

On 01/11/2016 06:55 PM, Fajar A. Nugraha wrote:
> On Tue, Jan 12, 2016 at 6:31 AM, Peter Steele <pwsteele at gmail.com> wrote:
>>  From what I've read, I understand that Amazon has implemented some
>> special/restricted behavior for the networking stack of EC2 instances. The
>> question I have is whether I can accomplish what I've attempted here,
>> specifically, can I access a LXC container hosted on one EC2 instance
>> directly from another EC2 instance or from another LXC container hosted on
>> another EC2 instance?
> You might want to ask them first. Looks like it's only available for
> VPC setup: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-eni.html#AvailableIpPerENI
>
> If they do allow multiple IP address, then the next step is to check
> whether they allow multiple MACs (which is what you get when you use
> bridge). There's a workaround for this if the ONLY limitation is the
> MAC, using proxyarp.
>
>
>