Steve Rukuts's questions

RDS offers encryption at rest, but this is incompatible with cross-region replication. The documentation states:

Because KMS encryption keys are specific to the region that they are created in, you cannot copy an encrypted snapshot from one region to another or replicate encrypted DB instances across regions.

However, it is now possible to upload a custom KMS master key. If I generate my own master key and upload it to both eu-west-1 and eu-central-1, is it possible to is it possible to replicate an encrypted RDS instance across regions?

The documentation does not say anything about this scenario. It's possible that it's now technically possible but the API does not permit it.

I am attempting to transfer a 1.3GB file from my local machine (Windows 8) to my local hyper-V instance (Windows 2012). The transfer begins at about 300kb/s and then swiftly drops to 12-20kb/s.

The two machines are connected to the LAN via the same physical ethernet adapter. The vSwitch and my local connection are bridged, so the VM and my local machine have IP addresses on the same subnet.

Could that be related to the issue? I not a network administrator by trade so I am unaware of the tricks to diagnose this issue.

At my office, there is a Windows Server 2008 router, 192.168.16.1, which is our default gateway. This sends data through our main internet connection. This works perfectly.

192.168.16.1 also has another internet connection that is currently sitting unused. This connects to a router, 192.168.1.254 which then connects to our secondary internet connection.

I have set up Routing and Remote Access to route the 192.168.1.* range to our internal network, and I am able to ping 192.168.1.254 from my desktop that has an IP address of 192.168.16.22.

I have a very intensive upload and download task for a linux box in the same office, so I want to set up a static route so I do not tie up our main internet connection and affect my co-workers. So, my plan is to set up this box with a static route.

From the linux box, I am able to ping 192.168.1.254, but I am unable to add a static route to the destination server in our data center:

$ sudo route add -host 123.123.123.123 gw 192.168.1.254 dev eth0
SIOCADDRT: No such process

From extensive googling, this error message seems to indicate that I am unable to access 192.168.1.254 to set up a route, yet I can ping it. I attempted to add a static route to 192.168.1.254, which worked perfectly, but this did not solve the issue (as expected).

I am not advanced enough at networking to diagnose this issue further as my background is software development, not system administration. I would be very grateful for any advice given.

Thank you for your time.