Archiving Proxy Appliance Detail Request

[micoolpaul]

Hi,

Apologies if this isn't the best place to post the question.

I'm trying to gleam some extra technical detail into the proxy appliance, as I need to provide extra detail & assurances to a security team as to what the proxy appliance VM will be based on & doing.

I'm trying to find out some specifics on which OS/Image is being used by AWS & Azure when an Archiving Appliance is created. I'm familiar with how this has worked historically for other types of proxy appliances with VMware & Hyper-V as you've been able to bring your own flp's and ISOs.

I'm presuming you're either using a standard Ubuntu image or similar, or otherwise you might have an image maintained by yourselves that you call. Without having this information to hand, it's difficult to know the security risk incurred whilst the virtual machine is running. This also brings me onto the next question, binaries. If it's a custom image maintained by yourselves, then it seems reasonable that you are using SSH to communicate to the virtual machine and run any binaries for object storage offloads to archive tier, and the binaries are pre-installed. If you're using a standard image however, unless the binaries you require are installed natively, you've got to deploy them, I can't see any firewall port requirements within the documentation for the proxy appliance to speak to any APT repositories for example, so I can only assume that otherwise the binaries are pushed over SSH to the Linux server too.

Apologies I'm not being 100% clear, but that's because I can see multiple avenues as to how this works, but I've not seen a technical write up on exactly WHAT the proxy appliance consists of in regards to OS + Binaries.

Any insights would be greatly appreciated!

[HannesK]

Hello,
yes, we use the Ubuntu image from AWS. APT is not needed. There is not even a DEB package at the moment So yes, we just push it via SSH.

Best regards,
Hannes

[micoolpaul]

Thank you

[Driberot]

Hello,
yes, we use the Ubuntu image from AWS. APT is not needed. There is not even a DEB package at the moment So yes, we just push it via SSH.

Best regards,
Hannes

Hi, one additional question. You push binaries through SSH on port 22 from VBR server to proxy appliance on which address (Public IP address) ? If so, it leads to security issues which are not compatible many restrictions with customers. Coudl you confirm ?

[Mildur]

Hi David

Yes, public IP address with the default configuration.
But you can use AWS private link. Then we will connect via VPN to the private IP address: https://www.veeam.com/kb4226

Best,
Fabian