Why need the archiver Appliance a Internet gateway?

[BennyDC]

Hi All

For a support case (#05736832) about slow copy jobs for Teams and SharePoint to a S3 bucket with Glacier Tagging.
We where advised to activate the archiver appliance. First we did run in a permission issue as the AWS account had only S3 access so we added
following this doc
"https://helpcenter.veeam.com/docs/vbo36 ... ge-classes"

The EC2 permissions. We are running this in a private VPC we were now able to see all settings with drop down boxes for E2 instance, Amazone VPC, Subnet and Security group.
All went fine but when we try to validate we get the message "VPC does not have an attached internet gateway". Yes that's true our private VPC doesn't has that but why is it needed?
All the components are in the same VPC and this appliance is only used to move data from 1 S3 bucket to another one.
Can anyone explain this? Does there exist a work around for this.

As always thanks for your thoughts and feedback

[Mike Resseler]

Hey Benny,

There is no workaround for this. The reason is that most proxies are (in this scenario) outside of Azure and therefore the appliance needs access to the internet. In the future we will think on how we can overcome the need for it, when all VB365 components are within the same cloud

[BennyDC]

Hi Mike,

I can understand this if we were talking about a proxy.
But this isn't a proxy but the archive helper appliance that launches a worker that needs to move data from a S3 bucket to another S3 bucket in the same VPC.
It doesn't need to connect to Azure.

[BennyDC]

Good news
Veeam support did give me a procedure change the Veeam Archiver proxy appliance.
I'm no able to mark the selection without message and it start now in our VPC.
However the next roadblock is that it gets a public ip. Instead one out of the range of the VPC.
I Keep working with support on it, will update once I have more info