As Steve indirectly pointed out above, an AWS VPC is not a real layer 2
domain.. so there's nothing really to "extend into".
The best way to conceptualise a VPC at a layer 2 level (at least from a
network engineer's perspective) is to imagine a full mesh of hosts,
connected by overlay tunnels,
Friends don't let friends build large layer2 networks!
That said; if you wanted to get a little creative you could run up a
csr1000v and setup otv and lisp from AWS to your on prem infra. I have
never set it up but would be interesting to see if the MP transport
supports it.
I guess the question
They are different.
Look for Hosted Connection VS AWS Direct Connect.
The connection you get via Megaport or all other Telcos most probably would
be Hosted Connection or Hosted VIF. Best to check with the telco – Megaport
in this instance on the product details, specs, limitations.
That’s still routed and not bridged over the DC. It’s all layer 3 over DCs
unless (as mentioned) you use an L2 tunnelling method onto a compute VM.
- Tim
> On 12 Feb 2019, at 19:01, Andras Toth wrote:
>
> I'm not sure if the Megaport Direct Connect is any different to a regular AWS
> Direct
I'm not sure if the Megaport Direct Connect is any different to a regular
AWS Direct Connect, but a friend of mine has successfully used a regular
AWS Direct Connect that they extended into their EC2 VPC and assigned IP
addresses to their instances from their own /28 range.
The subnet has a Route
