- Veeam Support Knowledge Base
- How to Configure Connections Required for Veeam Plug-In for Google Cloud in Highly Secured Environments
How to Configure Connections Required for Veeam Plug-In for Google Cloud in Highly Secured Environments
| KB ID: | 4157 |
| Product: |
Veeam Plug-In for Google Cloud | 5 | 6 | 7 Veeam Backup for Google Cloud | 1 | 2 | 3 | 4 |
| Published: | 2021-05-11 |
| Last Modified: | 2022-06-17 |
Get weekly article updates
Cheers for trusting us with the spot in your mailbox!
Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
Oops! Something went wrong.
Please, try again later.
If your backup appliance is deployed in a highly secured environment with all outbound connections restricted, you must perform the following configuration steps to make Veeam Plug-In for Google Cloud function properly:
- Allow internet access to the following Google Cloud APIs:
- Compute Engine API
- IAM Service Account Credentials API
- Identity and Access Management (IAM) API
- Cloud Resource Manager API
- Cloud Billing API
- Pub/Sub API
- Cloud Storage API
- Cloud Key Management Service API
- Cloud Logging API
To learn how to configure Private Google Access, see this Google Cloud KB article.
- Allow access to the Google Cloud metadata server that stores backup appliance metadata, to the NTP server that provides accurate timing to the backup appliance, and to the Cloud DNS server. To do that, create firewall rules to connect to the address 169.254.169.254 (metadata.google.internal) through the ports TCP 80 and UDP 53, 123
- Allow access to Ubuntu repositories that provide updates for the backup appliance. Ubuntu repositories are almost entirely defined by FQDNs that do not have static addresses behind them. That is why you can create the following firewall rules to receive the updates:
Destination Endpoint Protocol Port security.ubuntu.com TCP 80 - Allow access to the Microsoft update server that provides updates for Microsoft .NET Framework installed on the backup appliance. Update servers are almost entirely defined by FQDNs that do not have static addresses behind them. That is why you can create the following firewall rules to receive the updates:
Destination Endpoint Protocol Port packages.microsoft.com TCP 443 - Allow access to the SMTP server that sends email notifications for Veeam Plug-In for Google Cloud. SMTP servers are almost entirely defined by FQDNs that do not have static addresses behind them. That is why you can create the following firewall rules to send the notifications:
Destination Endpoint Protocol Port <FQDN of your SMTP server> TCP 587 - Allow access to the Veeam Update Notification Server that provides security updates for Veeam Plug-In for Google Cloud. The server is almost entirely defined by the FQDN that does not have static addresses behind it. That is why you can create the following firewall rules to receive the updates:
Destination Endpoint Protocol Port repository.veeam.com TCP 443
For all CLOUDFRONT service IP ranges, see this .JSON file.
If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.