Azure networking requirements Edit on GitHub
You must set up your Azure networking so that Cloud Manager can deploy ONTAP Cloud systems and so those systems can operate properly.
- Outbound internet access for Cloud Manager
Cloud Manager requires outbound internet access to contact the following endpoints when deploying and managing ONTAP Cloud in Microsoft Azure:
Enables Cloud Manager to deploy and manage ONTAP Cloud systems in most Azure regions.
Enables Cloud Manager to deploy and manage ONTAP Cloud systems in the Azure Germany regions.
Enables Cloud Manager to deploy and manage ONTAP Cloud systems in the Azure US Gov regions.
Provides access to software images, manifests, and templates.
Enables Cloud Manager to access and download manifests, templates, and ONTAP Cloud upgrade images.
Enables NetApp to stream data from audit records.
Communication with NetApp Cloud Central for centralized user authentication.
Communication with NetApp AutoSupport.
Communication with NetApp for licensing and support registration.
Various third-party locations, for example:
Third-party locations are subject to change.
During upgrades, Cloud Manager downloads the latest packages for third-party dependencies.
If your network uses a proxy server for all communication to the internet, Cloud Manager prompts you to specify the proxy during setup. You can also specify the proxy server from the Settings page. Refer to Configuring Cloud Manager to use a proxy server.
- Outbound internet access for ONTAP Cloud
ONTAP Cloud requires outbound internet access to send messages to NetApp AutoSupport, which proactively monitors the health of your storage.
Routing and firewall policies must allow Azure HTTP/HTTPS traffic to mysupport.netapp.com so ONTAP Cloud can send AutoSupport messages.
- Outbound internet access from your web browser
Users must access Cloud Manager from a web browser. A web browser must have connections to the following endpoints:
The Cloud Manager host
You must enter the host’s IP address from a web browser to load the Cloud Manager console.
If you deploy Cloud Manager in Azure, the easiest way to provide access is by allocating a public IP address. However, if you want to use a private IP address instead, users can access the console through either of the following:
A jump host in the VNet that has a connection to Cloud Manager
A host in your network that has a VPN connection to the private IP address
Your web browser connects to this endpoint for centralized user authentication through NetApp Cloud Central.
- Security groups
You do not need to create security groups because Cloud Manager does that for you. If you need to use your own, refer to Security group rules.
- Connection between Cloud Manager and ONTAP Cloud subnets
Cloud Manager requires a connection to the subnets in which you deploy ONTAP Cloud systems.
If Cloud Manager is not installed in the target VNet, it must have network connectivity to that VNet. For example, if you install Cloud Manager in AWS or in your corporate network, you must set up a VPN connection to the VNet in which you deploy ONTAP Cloud systems.
- Connections to ONTAP systems in other networks
To replicate data between an ONTAP Cloud system in Azure and ONTAP systems in other networks, you must have a VPN connection between the Azure VNet and the other network—for example, an AWS VPC or your corporate network.
For instructions, refer to Microsoft Azure Documentation: Create a Site-to-Site connection in the Azure portal.