new VBA, high NATGateway charge

[kyw]

Yesterday I deployed an Veeam backup for AWS (VBA) and tried to backup one of our EC2 with around 3TB EBS using the VBA to S3.

Today I check our latest Oct bills and found the following charge:
Amazon Elastic Compute Cloud NatGateway $91.61
$0.065 per GB Data Processed by NAT Gateways 555.313 GB $36.10
$0.065 per NAT Gateway Hour 854.000 Hrs $55.51

I read the VBA documentations and didn't find anything about the NATGateway charge
Is using VBA will cause the NATGateway charge and why?

My VBA instance is at the same subnet as my backup target EC2 instanace, my backup worker is also configurated at the same subnet.

[jorgedlcruz]

Hello,
What does the policy cost estimator says?

One quick thing to verify is to be using endpoints correctly so no gateway is needed https://www.veeam.com/kb3197

I do not recall a NAT Gateway to be required on the multiple labs I did, but perhaps your environment is much more complex.

Please confirm all the endpoints are configured properly.

Thank you

[nielsengelen]

Is your s3 Bucket in the same region as the production instance?
Did you assign an elastic IP by any chance to the VBA instance?
Can you share more details about your subnet setup, is it a public or private one?

[kyw]

1. Yes it's the same region
2. No elasitc IP assigned
3. it's a private subnet

I googled and I think I need to add a "vpc endpoint gateway" to have my ec2 subnet direct route to the S3 without route via the internet (NAT gateway)

I think Veeam should be clearly document about this. I think I spent USD200 for backup 3TB EBS to S3, routed via the NAT gateway.

[nielsengelen]

We have this noted in our user guide on how to configure this. Normally, the policy summary should give you a message as well if public IP assignment is off that links to this page.

Please verify if this is the case for you and if configuring the endpoints resolves the issues.