Is crazy to even think about installing RouterOS on a Cloud instance?
I am not sure this is possible. Although would be pretty darn cool.
I have a RB1000 hotspot controller for hotspots all over North America, it would be nice to be able to leverage the Amazon peering by moving it there. RIght now I have to worry about localized Internet issues knocking out systems all over the place and Amazon has super cheap bandwidth.
Also could make a nice VPN Server, central to people all over the world really. Especially when many corporate servers are hosted on the cloud now.
it seem syou are able to install x86 there (as windows is there running) so you can create some usermanager instance there, and making hotspots to authorize against that server. But not sure about other benefits.
i think its an awesome idea. I dont think amazon supports all kernels though, from the page you referenced:
“An AMI does not include a kernel image, only a pointer to the default kernel id, which can be chosen from an approved list of safe kernels maintained by Amazon and its partners (e.g., RedHat, Canonical, Microsoft). Users may choose kernels other than the default when booting an AMI.[3]”
I dont understand that last sentence fully, does that mean you can use your own kernel? Maybe I will try it late one night…
only few cpus allow running guest OS into the guest, and most of them come from AMD. I really doubt that amazon is running those CPUs for their cloud installation.
Well, this stuff made me curious so I’ve created a VMWare image of the newest ROS, converted it into the appropriate format, uploaded to S3 (where the C2 cloud can import it)… only to find out in the end that this method only works for Windows operating systems. There is, however, another possibility. A running EC2 Linux instance can create another one with basically anything running in it. That’s something I haven’t looked into yet, I lack the free time for this experiment. Other than this, it would be quite an achievement to see ROS included as a standard offering in the EC2 infrastructure.
everything regarding XEN virtualization is disabled. Only chance would be to load RouterOS 3.x and all versions till introduction of KVM as VMS in RouterOS.
I shot an email about 2 years ago asking if they would want to run Mikrotik as a service in aws. I told them I would help run the project too. They didn’t want anything to do with it and told me I could do it myself if I were willing to be a reseller and purchase a bunch of licenses and resell each license per instance ahead of time. The tone of the email was somewhat of a “You are not worth my time” tone. I don’t know if they just didn’t know what I was talking about or something got lost in translation but they were somewhat rude.
This does work for linux instances too. I actually tried a direct import of routeros from vmware (not s3) through the AWS VMware Connector but it failed. I’m thinking there’s a kernel issue because they only allow kernels with certain things compiled into it.
I know almost nothing about Azure, but wouldn’t it be reasonable to assume that it shares code with Hyper-V? If so, wouldn’t drivers for ethernet interfaces be a problem (see other Hyper-V threads)?
