Well, I wouldn’t write this topic if it wasn’t clearly stated that feedback is welcomed
It is an interesting and, in some way, unique service. However I’m very disappointed by the network design.
It was very unexpected to discover a routed L3 network.
I’m used to construct the cloud topology as I want and to assign the desired IP addresses without sharing the address space with all the customers of the service.
I was surprised by strange ARP requests arriving on my server’s network interface. Most probably this has no impact on security. Nevertheless, It’s not very encouraging and, being suspicious by nature, I find it strange.
Damn, when i want to connect a “private” instance without public IP to the internet via a “public” instance, I can’t even do it without a “dirty” workaround like a proxy or an GRE/IPIP tunnel. It’s silly for a “cloud” platform…
I don’t even understand the reasons besides this choice. Why not give the customer the right to design his own L2 network. If it is not an commercial secret, can u please tell the community why is there an routed L3 network shared among all the customers and not a “beautiful”, “classical”, private L2 achieved via MPLS or VXLANS?
Just an angry customer.