Helper appliance connection problem

[Cskollar]

Hello,

We synchronize backups from a Veeam AWS appliance to an on-prem Veeam B&R with copy jobs. Our on-prem backup network is highly secure, connections to public directions are restricted and controlled by firewall rules. In the case of a restore task, we cannot anticipate the IP address of the helper appliance in advance, as it will be a dynamically assigned public address provided by AWS. Therefore, we cannot create an allowing firewall rule to enable the on-prem Veeam components to reach the temporary helper appliance.

We don't want to allow all HTTPS traffic from the backup network without filtering. Is there any other solution or best practice for this problem?

[Cskollar]

Why moved this topic from "Veeam for AWS" to "Veeam R&D"? There is no context here, it doesn't make sense. The essential part of the question is about the Veeam for AWS helper appliance.

[Mildur]

Hello CsKollar

Veeam Backup for AWS is a separate product:
https://helpcenter.veeam.com/docs/vbaws ... tml?ver=70

Helper appliance for restores in AWS to EC2 is a feature from Veeam Backup & Replication:
https://helpcenter.veeam.com/docs/backu ... ml?ver=120

Your question is about our VBR feature "Helper appliance". That's probably the reason why it was moved.

It is currently not possible to specify a public IP address for our helper appliances in VBR (health check, archiver, restore). But we got the request from other customers as well.
Unfortunately I cannot provide you with an ETA or version when it may be delivered.

What you can do today is to leverage PrivateLink/DirectConnect. This will allow you to connect to the restore helper appliance through private IPs instead of a public address.

Best,
Fabian