--- title: "Configure site information" canonical: "https://docs.aryaka.com/space/KNOW/1511548/Configure%20site%20information" format: markdown --- Site configuration varies based on the type of site you are configuring, but typically involves selecting your site type, location, and license tier, and configuring any required redundancy features. For descriptions of the different site types, bandwidth tiers, and location types, see the Site types overview topic. The fields on the Site Information tab change dynamically depending on what type of site you are creating. Click the following links to display the instructions for creating each type of site: The Site Information tab appears by default when you click the  Add icon on the Sites page. To access this page for an existing site, select a site from the list on the Sites page and click View on the Site Details tile displayed. Open the Site Information tab from the Add Sites page if it is not already open. Configure the following fields in the Site Details section: Select Global or Regional from the Site Type drop-down list based on the remote connectivity required by the site.  Select On Premises from the Location Type drop-down list. Enter a name for this site in the Site Name field. (Optional) Enter a code in the Site Code field. This is intended to be a shorthand version of the site name or an organizational device. For example, if you are creating four sites in North America, you could create a North America site code to classify the four sites. (Optional) Select a user from the Technical Contact drop-down list (it defaults to the current user) or click Add New and create a new contact. Click the Site License Type drop-down list, then select one of the following license types: BYO (Bring your own, meaning no ANAP is provided by Aryaka) Small Medium Large XLarge 2XLarge 5XLarge 10XLarge Configure the following fields in the Site Bandwidth section: Enter the bandwidth (in Mbps) that you contracted Aryaka to provide for this site in the Subscribed Bandwidth field. Click  Yes in the Bursting field if you want this site to be capable of sending bursts of traffic in excess of the subscribed bandwidth. By default, this field is set to No, and the site's throughput is limited to the subscribed bandwidth. Note: Aryaka charges extra for this feature. Contact your Aryaka account representative for details. Configure the following fields if L3 Private Core is enabled by Aryaka support. These fields only appear in the Edit Site mode—they do not appear during the Add Site procedure and are subject to the criteria described in L3 private core : Click the Advanced tab to display the advanced bandwidth settings. Accept the default setting in the Total Site Bandwidth field. The default is equal to the subscribed bandwidth if bursting is off, and the burst factor times the subscribed bandwidth if bursting is on. Note that if you edit this field, or the Subscribed Bandwidth field, the value in the Total Site Bandwidth field cannot be less the the subscribed bandwidth times the bursting factor.  Enter the bandwidth (in Mbps) that is reserved for the L2 private core in the L2 Private Core Reserve field.  (Optional) Configure the following fields in the Site Add-Ons section: Click the Redundancy Type drop-down list and select one of the following types of redundancy required at the site: POP HA with BGP—The site has POP redundancy. The site being created is the primary site. The backup site is created by Aryaka Support in the backend. Both sites may or may not have an ANAP. If they do have ANAPs, their LAN connects to an L3 device and BGP is configured between the ANAP and the L3 device.  ANAP HA with VARP—The site has ANAP redundancy. Both ANAP’s LAN connect to an L2 device. The VARP is configured between the ANAPs. POP HA with VARP—The site has POP redundancy. The site being created is the primary site. The backup site is created by Aryaka Support in the backend. Both sites must have an ANAP and their LAN connects to an L2 device. The VARP is configured between the ANAPs.  POP HA with ANAP HA—The site has ANAP and POP redundancy. Requires two pairs of ANAPs (four devices total).  Click the SWG toggle to turn it to the on position if you have purchased Aryaka SmartSecure NGFW-SWG or Advanced Security for the site. The Anti-Malware, IPS, CASB, and DLP toggles appear.  Click the toggles to enable the add-on services you have purchased for the site. Configure the following fields in the Site Address section: (Optional) Edit the Company Name field if you do not want to use the default company name. Enter the company's street address in the Address Line 1 field. (Optional) Enter additional address information (for example suite or floor number) in the Address Line 2, 3, and 4 fields as appropriate. Enter the site's country, zip code, city, and state in the corresponding fields. Ensure the Yes option is selected in the read-only Aryaka Will Provide SD-WAN Device (ANAP) field, then configure the following fields in the Connectivity Specification section: ANAP Device Form Factor—Select Physical (you must install the ANAP device at the site) or Virtual (you must install the ANAP's image onto your on-premises device as described in Download a virtual ANAP image . IPSec IP Address Type—Select Static or Dynamic as appropriate. If you select Static, the Public IP for IPSec field appears in the Primary ISP Link section (step 7b); if you select Dynamic, the IPSec IKE ID field appears in the Primary ISP Link section (step 7b). Is IP Address Shared by Other Tunnels (in the Primary ISP Link section)—Click Yes or No depending on whether the primary ISP is shared by other tunnels. Configure the fields in the Primary ISP Link section: Enter the name of your primary ISP or telecommunications carrier in the Primary ISP Provider Name field. Enter your company’s primary IPv4 address or fully-qualified domain name (FQDN) in the Public IP for IPSec or IPSec IKE ID field (the field that appears is determined by the selection you made in the IPSec IP Address Type field in step 6). This specifies the source of the primary IPsec tunnel used to communicate with the Aryaka. (Optional) Enter the IPv4 address that you want Aryaka to monitor. If you do not make an entry in this field, your primary, public IP address is monitored. If you have not already selected Yes or No in the Is IP Address Shared by Other Tunnels field (in step 6), do so now.  Enter the maximum amount of traffic you can upload to your primary ISP in the Uplink Size (Mbps) field. This is the rate specified in the contact with your ISP. Enter the maximum amount of traffic you can download from your primary ISP in the Downlink Size (Mbps) field. This is the rate specified in the contact with your ISP. (Optional) Click the Secondary ISP Link toggle if you are using a secondary ISP to access the Internet when your primary ISP is unavailable. Note that this option is only available after you have configured a primary ISP. Configure the following fields that appear in the section: Enter the name of your secondary ISP or telecommunications carrier in the Secondary ISP Provider Name field. Enter your company’s secondary IPv4 address or fully-qualified domain name (FQDN) in the Public IP for IPSec or FQDN field. This specifies the source of the secondary IPsec tunnel used to communicate with the Aryaka. (Optional) Enter the IPv4 address that you want Aryaka to monitor. If you do not make an entry in this field, your secondary, public IP address is monitored. Enter the maximum amount of traffic you can upload to your secondary ISP in the Uplink Size (Mbps) field. This is the rate specified in the contact with your secondary ISP. Enter the maximum amount of traffic you can download from your secondary ISP in the Downlink Size (Mbps) field. This is the rate specified in the contact with your secondary ISP. (Optional) Click the Tertiary ISP Link toggle if you are using a tertiary ISP to access the Internet when your primary and secondary ISPs are unavailable. Note that this option is only available after you have configured a secondary ISP. Configure the following fields that appear in the section: Enter the name of your tertiary ISP or telecommunications carrier in the Tertiary ISP Provider Name field. (Optional) Enter the IPv4 address that you want Aryaka to monitor. If you do not make an entry in this field, your tertiary, public IP address is monitored. Enter the maximum amount of traffic you can upload to your tertiary ISP in the Uplink Size (Mbps) field. This is the rate specified in the contact with your tertiary ISP. Enter the maximum amount of traffic you can download from your tertiary ISP in the Downlink Size (Mbps) field. This is the rate specified in the contact with your tertiary ISP. Do one of the following: Click Save Draft to save a draft of the entries made on this page. Click the Next icon or the  ANAP Info icon to continue your site configuration on the ANAP Info tab as described in  Configure ANAP Information . Click Submit to send a change request with the entries made on this page to Aryaka support. Open the Site Information tab from the Add Sites page if it is not already open. Configure the following fields in the Site Details section: Select Global or Regional from the Site Type drop-down list based on the remote connectivity required by this site.  Select Virtual Office  from the Location Type drop-down list. Enter a name for this site in the Site Name field. (Optional) Enter a code in the Site Code field. This is intended to be a shorthand version of the site name or an organizational device. For example, if you are creating four sites in North America, you could create a North America site code to classify the four sites. (Optional) Select a user from the  Technical Contact  drop-down list or click  Add New  and create a new contact. Select one of the following license types from the Site   License Type drop-down list: BYO (Bring your own, meaning no ANAP is provided by Aryaka) Small Medium Large XLarge 2XLarge 5XLarge 10XLarge Configure the following fields in the Site Bandwidth section Enter the bandwidth (in Mbps) that you contracted Aryaka to provide for this site in the Subscribed Bandwidth field. Click  Yes in the Bursting field if you want this site to be capable of sending bursts of traffic up to 1.5 times in excess of the subscribed bandwidth. By default, this field is set to No, and the site's throughput is limited to the subscribed bandwidth. Note: Aryaka charges extra for this feature. Contact your Aryaka account representative for details. Configure the following fields if L3 Private Core is enabled by Aryaka support. These fields only appear in the Edit Site mode—they do  not  appear during the Add Site procedure and are subject to the criteria described in  L3 private core : Click the  Advanced  tab to display the advanced bandwidth settings. Accept the default setting in the Total Site Bandwidth field. The default is equal to the subscribed bandwidth if bursting is off, and the burst factor times the subscribed bandwidth if bursting is on. Enter the bandwidth (in Mbps) that is reserved for the L2 private core in the L2 Private Core Reserve field.  (Optional) In the Site Add-Ons section, click the Redundancy Type drop-down list and select POP HA with BGP if POP redundancy is required at the site. Note that the site being created is the primary site. The backup site is created by Aryaka Support in the backend. Configure the following fields in the Site Address section: (Optional) Edit the Company Name field if you do not want to use the default company name. Enter the site's country, zip code, city, and state in the corresponding fields. Do one of the following: Click either the Next  icon or the Site to Site Topology  icon to continue your site configuration on the Site to Site Topology tab as described in Configure site to site topology . Click Submit to send a change request with the entries made on this page to Aryaka support. Open the Site Information tab from the Add Sites page if it is not already open. Configure the following fields in the Site Details section: Select IaaS  from the Site Type drop-down list. The Location Type field automatically displays Hosted Cloud. See the IaaS  topics for details on this site type and location. Enter a name for this site in the Site Name field. (Optional) Enter a code in the Site Code field. This is intended to be a shorthand version of the site name or an organizational device. For example, if you are creating four sites in North America, you could create a North America site code to classify the four sites. (Optional) Select a user from the Technical Contact drop-down list or click Add New and create a new contact. Click the Site License Type drop-down list, then select one of the following license types: Legacy Small Medium Large XLarge  2XLarge 5XLarge 10XLarge Configure the following fields in the Site Bandwidth section: Enter the bandwidth (in Mbps) that you contracted Aryaka to provide for this site in the Subscribed Bandwidth field. Click  Yes in the Bursting field if you want this site to be capable of sending bursts of traffic in excess of the subscribed bandwidth. By default, this field is set to No, and the site's throughput is limited to the subscribed bandwidth. Note: Aryaka charges extra for this feature. Contact your Aryaka account representative for details. Configure the following fields if L3 Private Core is enabled by Aryaka support. These fields only appear in the Edit Site mode—they do  not  appear during the Add Site procedure and are subject to the criteria described in L3 private core : Click the  Advanced  tab to display the advanced bandwidth settings. Accept the default setting in the Total Site Bandwidth field. The default is equal to the subscribed bandwidth if bursting is off, and the burst factor times the subscribed bandwidth if bursting is on. Note that if you edit this field, or the Subscribed Bandwidth field, the value in the Total Site Bandwidth field cannot be less the the subscribed bandwidth times the bursting factor.  Enter the bandwidth (in Mbps) that is reserved for the L2 private core in the L2 Private Core Reserve field.  (Optional) Configure the following fields in the Site Add-Ons section: Click the Redundancy Type drop-down list and select POP HA with BGP if POP redundancy is required at the site. Note that the site being created is the primary site. The backup site is created by Aryaka Support in the backend. Click the SWG toggle to turn it to the on position if you have purchased Aryaka SmartSecure NGFW-SWG or Advanced Security for the site. The Anti-Malware, IPS, CASB, and DLP toggles appear.  Click the toggles to enable the add-on services you have purchased for the site. In the Cloud Instance Details section, click the Deployment Type drop-down list, select the type of connection you want to use between the Aryaka POP and the cloud service, and then complete the corresponding procedure: Private Connect: Configure the following fields in the Cloud Instance Details section: Click the  Cloud Service  drop-down list, then select your cloud service provider. If you have not already, click the Deployment Type drop-down list, then select Private Connect . Click the Peering Type drop-down list, then select one of the following options: Private—The resources in the instance are accessible only from within your organization. Public—The resources in the instance are accessible from the public internet. If you select this option, the NAT IP field appears if the Aryaka Provides IP toggle is disabled. Enter a public IPv4 IP to be used for natting. Based on the Cloud Service selected and backend configuration, Instance Identifier fields prompt you for information provided by the cloud service portal. Enter the requested information in the following field if they appears:  Account ID Service Key VPC ID Click the Instance Region drop-down list, then select the geographic region where the instance is deployed. If the region is not listed, select Other and enter the region of your instance in the Other Region field that appears.  (Optional) Enter a description of this site or any other appropriate comment in the Description field. Secure VPN Configure the following fields in the Cloud Instance Details section: Click the  Cloud Service  drop-down list, then select your cloud service provider. If you have not already, click the  Deployment Type  drop-down list, then select Secure VPN. Configure the following fields in the Connectivity Specification section: Click Yes or  No in the Aryaka Will Provide SD-WAN Device (ANAP) field. If you click No, the IPsec Device defaults to the Aryaka-defined router profile and the ANAP Info icon—and corresponding tab—are removed from the UI. If you click Yes, select one of the following options from the ANAP Device Form Factor field that appears. Physical—You must install the ANAP device at the site. Virtual—You must install the ANAP's image onto your on-premises device. The V-ANAP Image and Details field appears at the top of the Site Details pane. See Download a virtual ANAP image for detailed instructions. If the Aryaka Will Provide SD-WAN Device (ANAP) is set to Yes, configure the following fields in the Tunnel Configuration section: Ensure the Custom Settings toggle is off.  Enter your cloud service provider's primary IPv4 address in the Primary Tunnel IP field. This specifies the source of the primary IPsec tunnel used to communicate with the Aryaka. Enter the Pre-Shared Key (PSK) associated with the primary tunnel in Primary Tunnel PSK field. This is generated by the cloud service provider while creating the IPsec tunnel in their administration portal. (Optional) Enable a secondary tunnel if redundancy is required and if you have created a secondary tunnel in the portal as follows: Click the Security Tunnel toggle to on. Two secondary tunnel fields appear. Enter your cloud service provider's secondary IPv4 address in the Secondary Tunnel IP field. This specifies the source of the secondary IPsec tunnel used to communicate with the Aryaka. Enter the Pre-Shared Key associated with the secondary tunnel in Secondary Tunnel PSK field. This can be the same as Primary Tunnel PSK. Click the IKE Version drop-down list and select the version that is configured in the cloud service portal. (Optional) Click the  Advanced tab to configure Phase 1 and Phase 2 properties of the IPsec tunnel using the entries in the IPsec tunnels' configuration file available in the cloud service providers portal. If the required Phase 1 or Phase 2 options are not included in the drop-down lists, you can share the cloud service configuration file with Aryaka Support as follows: Open a new browser tab, navigate to https://files.aryaka.com/ and log in with your MyAryaka credentials. The Files page appears. Click Upload , then drag the IPsec configuration file onto the Upload Files tab. Copy the entire path to this file. Return to the Site Information tab in MyAryaka, then click the Custom Settings toggle to on in the Tunnel Configuration section. Paste the path to the configuration file in the Enter IPSec Configuration Details field.  (Optional) Enter a description of this site or any other appropriate comment in the Description field. Internet In the Cloud Instance Details section, click the Cloud Service  drop-down list, then select your cloud service provider.  Click the Deployment Type drop-down list, then select Internet. Do one of the following: Click the ANAP Info  icon to continue your site configuration on the ANAP Info tab as described in Configure ANAP Information . Click the Site to Site Topology  icon to continue your site configuration on the Site to Site Topology tab as described in Configure site to site topology . Click the Next  icon. The ANAP tab appears if you are using an ANAP. The Site to Site Topology tab appears if you are not using an ANAP. Click Submit to send a change request with the entries made on this page to Aryaka support. Open the Site Information tab from the Add Sites page if it is not already open. Configure the following fields in the Site Details section: Select SD-WAN , Unified SASE , or Advanced Security from the Site Type drop-down list.  Select On Premises from the Location Type drop-down list. Enter a name for this site in the Site Name field. (Optional) Enter a code in the Site Code field. This is intended to be a shorthand version of the site name or an organizational device. For example, if you are creating four sites in North America, you could create a North America site code to classify the four sites. (Optional) Select a user from the Technical Contact drop-down list (it defaults to the current user) or click Add New and create a new contact. Click the Site License Type drop-down list, then select one of the following license types: Small Medium Large XLarge 2XLarge 5XLarge 10XLarge (Optional) In the Site Add-Ons section, click the Redundancy Type drop-down list and select one of the following types of redundancy required at the site: POP HA with BGP—The site has POP redundancy. The site being created is the primary site. The backup site is created by Aryaka Support in the backend. Both sites may or may not have an ANAP. If they do have ANAPs, their LAN connects to an L3 device and BGP is configured between the ANAP and the L3 device.  ANAP HA with VARP—The site has ANAP redundancy. Both ANAP’s LAN connect to an L2 device. The VARP is configured between the ANAPs. POP HA with VARP—The site has POP redundancy. The site being created is the primary site. The backup site is created by Aryaka Support in the backend. Both sites must have an ANAP and their LAN connects to an L2 device. The VARP is configured between the ANAPs.  POP HA with ANAP HA—The site has ANAP and POP redundancy. Requires two pairs of ANAPs (four devices total).  Configure the following fields in the Site Address section: (Optional) Edit the Company Name field if you do not want to use the default company name. Enter the company's street address in the Address Line 1 field. (Optional) Enter additional address information (for example suite or floor number) in the Address Line 2, 3, and 4 fields as appropriate. Enter the site's country, zip code, city, and state in the corresponding fields. Ensure the Yes option is selected in the read-only Aryaka Will Provide SD-WAN Device (ANAP) field, then configure the following fields in the Connectivity Specification section: ANAP Device Form Factor—Select Physical (you must install the ANAP device at the site) or Virtual (you must install the ANAP's image onto your on-premises device as described in Download a virtual ANAP image . IPSec IP Address Type—Select Static or Dynamic as appropriate. If you select Static, the Public IP for IPSec field appears in the Primary ISP Link section (step 7b); if you select Dynamic, the IPSec IKE ID field appears in the Primary ISP Link section (step 7b). Is IP Address Shared by Other Tunnels (in the Primary ISP Link section)—Click Yes or No depending on whether the primary ISP is shared by other tunnels. Configure the fields in the Primary ISP Link section: Enter the name of your primary ISP or telecommunications carrier in the Primary ISP Provider Name field. Enter your company’s primary IPv4 address or fully-qualified domain name (FQDN) in the Public IP for IPSec or IPSec IKE ID field (the field that appears is determined by the selection you made in the IPSec IP Address Type field in step 6). This specifies the source of the primary IPsec tunnel used to communicate with the Aryaka. (Optional) Enter the IPv4 address that you want Aryaka to monitor. If you do not make an entry in this field, your primary, public IP address is monitored. If you have not already selected Yes or No in the Is IP Address Shared by Other Tunnels field (in step 6), do so now.  Enter the maximum amount of traffic you can upload to your primary ISP in the Uplink Size (Mbps) field. This is the rate specified in the contact with your ISP. Enter the maximum amount of traffic you can download from your primary ISP in the Downlink Size (Mbps) field. This is the rate specified in the contact with your ISP. (Optional) Click the Secondary ISP Link toggle if you are using a secondary ISP to access the Internet when your primary ISP is unavailable. Note that this option is only available after you have configured a primary ISP. Configure the following fields that appear in the section: Enter the name of your secondary ISP or telecommunications carrier in the Secondary ISP Provider Name field. Enter your company’s secondary IPv4 address or fully-qualified domain name (FQDN) in the Public IP for IPSec or FQDN field. This specifies the source of the secondary IPsec tunnel used to communicate with the Aryaka. (Optional) Enter the IPv4 address that you want Aryaka to monitor. If you do not make an entry in this field, your secondary, public IP address is monitored. Enter the maximum amount of traffic you can upload to your secondary ISP in the Uplink Size (Mbps) field. This is the rate specified in the contact with your secondary ISP. Enter the maximum amount of traffic you can download from your secondary ISP in the Downlink Size (Mbps) field. This is the rate specified in the contact with your secondary ISP. (Optional) Click the Tertiary ISP Link toggle if you are using a tertiary ISP to access the Internet when your primary and secondary ISPs are unavailable. Note that this option is only available after you have configured a secondary ISP. Configure the following fields that appear in the section: Enter the name of your tertiary ISP or telecommunications carrier in the Tertiary ISP Provider Name field. (Optional) Enter the IPv4 address that you want Aryaka to monitor. If you do not make an entry in this field, your tertiary, public IP address is monitored. Enter the maximum amount of traffic you can upload to your tertiary ISP in the Uplink Size (Mbps) field. This is the rate specified in the contact with your tertiary ISP. Enter the maximum amount of traffic you can download from your tertiary ISP in the Downlink Size (Mbps) field. This is the rate specified in the contact with your tertiary ISP. Do one of the following: Click Save Draft to save a draft of the entries made on this page. Click the Next icon or the  ANAP Info icon to continue your site configuration on the ANAP Info tab as described in  Configure ANAP Information . Click Submit to send a change request with the entries made on this page to Aryaka support. Open the Site Information tab from the Add Sites page if it is not already open. Configure the following fields in the Site Details section: Select SD-WAN from the Site Type drop-down list.  Select Virtual Office  from the Location Type drop-down list. Enter a name for this site in the Site Name field. (Optional) Enter a code in the Site Code field. This is intended to be a shorthand version of the site name or an organizational device. For example, if you are creating four sites in North America, you could create a North America site code to classify the four sites. (Optional) Select a user from the  Technical Contact  drop-down list or click  Add New  and create a new contact. Select one of the following license types from the Site   License Type drop-down list: Small Medium Large XLarge 2XLarge 5XLarge 10XLarge (Optional) In the Site Add-Ons section, click the Redundancy Type drop-down list and select POP HA with BGP if POP redundancy is required at the site. Note that the site being created is the primary site. The backup site is created by Aryaka Support in the backend. Configure the following fields in the Site Address section: (Optional) Edit the Company Name field if you do not want to use the default company name. Enter the site's country, zip code, city, and state in the corresponding fields. Do one of the following: Click either the Next  icon or the Site to Site Topology  icon to continue your site configuration on the Site to Site Topology tab as described in Configure site to site topology . Click Submit to send a change request with the entries made on this page to Aryaka support. Open the Site Information tab from the Add Sites page if it is not already open. Configure the following fields in the Site Details section: Select SD-WAN , Unified SASE , or Advanced Security from the Site Type drop-down list. Select Hosted Cloud  from the Location Type drop-down list. Enter a name for this site in the Site Name field. (Optional) Enter a code in the Site Code field. This is intended to be a shorthand version of the site name or an organizational device. For example, if you are creating four sites in North America, you could create a North America site code to classify the four sites. (Optional) Select a user from the Technical Contact drop-down list or click Add New and create a new contact. Click the Site License Type drop-down list, then select one of the following license types: Small Medium Large XLarge  2XLarge 5XLarge 10XLarge (Optional) In the Site Add-Ons section, Click the Redundancy Type drop-down list and select POP HA with BGP if POP redundancy is required at the site. Note that the site being created is the primary site. The backup site is created by Aryaka Support in the backend. In the Cloud Instance Details sections, click the Deployment Type drop-down list and select the type of connection you want to use between the Aryaka POP and the cloud service, and then complete the corresponding procedure: Private Connect: Configure the following fields in the Cloud Instance Details section: Click the  Cloud Service  drop-down list, then select your cloud service provider. If you have not already, click the Deployment Type drop-down list, then select Private Connect . Click the Peering Type drop-down list, then select one of the following options: Private—The resources in the instance are accessible only from within your organization. Public—The resources in the instance are accessible from the public internet. If you select this option, the NAT IP field appears if the Aryaka Provides IP toggle is disabled. Enter a public IPv4 IP to be used for natting. Based on the Cloud Service selected and backend configuration, Instance Identifier fields prompt you for information provided by the cloud service portal. Enter the requested information in the following field if they appears:  Account ID Service Key VPC ID Click the Instance Region drop-down list, then select the geographic region where the instance is deployed. If the region is not listed, select Other and enter the region of your instance in the Other Region field that appears.  (Optional) Enter a description of this site or any other appropriate comment in the Description field. Secure VPN Configure the following fields in the Cloud Instance Details section: Click the  Cloud Service  drop-down list, then select your cloud service provider. If you have not already, click the  Deployment Type  drop-down list, then select Secure VPN. Configure the following fields in the Connectivity Specification section: Click Yes or  No in the Aryaka Will Provide SD-WAN Device (ANAP) field. If you click No, the IPsec Device defaults to the Aryaka-defined router profile and the ANAP Info icon—and corresponding tab—are removed from the UI. If you click Yes, select one of the following options from the ANAP Device Form Factor field that appears. Physical—You must install the ANAP device at the site. Virtual—You must install the ANAP's image onto your on-premises device. The V-ANAP Image and Details field appears at the top of the Site Details pane. See Download a virtual ANAP image for detailed instructions. If the Aryaka Will Provide SD-WAN Device (ANAP) is set to Yes, configure the following fields in the Tunnel Configuration section: Ensure the Custom Settings toggle is off.  Enter your cloud service provider's primary IPv4 address in the Primary Tunnel IP field. This specifies the source of the primary IPsec tunnel used to communicate with the Aryaka. Enter the Pre-Shared Key (PSK) associated with the primary tunnel in Primary Tunnel PSK field. This is generated by the cloud service provider while creating the IPsec tunnel in their administration portal. (Optional) Enable a secondary tunnel if redundancy is required and if you have created a secondary tunnel in the portal as follows: Click the Security Tunnel toggle to on. Two secondary tunnel fields appear. Enter your cloud service provider's secondary IPv4 address in the Secondary Tunnel IP field. This specifies the source of the secondary IPsec tunnel used to communicate with the Aryaka. Enter the Pre-Shared Key associated with the secondary tunnel in Secondary Tunnel PSK field. This can be the same as Primary Tunnel PSK. Click the IKE Version drop-down list and select the version that is configured in the cloud service portal. (Optional) Click the  Advanced tab to configure Phase 1 and Phase 2 properties of the IPsec tunnel using the entries in the IPsec tunnels' configuration file available in the cloud service providers portal. If the required Phase 1 or Phase 2 options are not included in the drop-down lists, you can share the cloud service configuration file with Aryaka Support as follows: Open a new browser tab, navigate to https://files.aryaka.com/ and log in with your MyAryaka credentials. The Files page appears. Click Upload , then drag the IPsec configuration file onto the Upload Files tab. Copy the entire path to this file. Return to the Site Information tab in MyAryaka, then click the Custom Settings toggle to on in the Tunnel Configuration section. Paste the path to the configuration file in the Enter IPSec Configuration Details field.  (Optional) Enter a description of this site or any other appropriate comment in the Description field. Internet In the Cloud Instance Details section, click the Cloud Service  drop-down list, then select your cloud service provider.  Click the Deployment Type drop-down list, then select Internet. Do one of the following: Click the ANAP Info  icon to continue your site configuration on the ANAP Info tab as described in Configure ANAP Information . Click the Site to Site Topology  icon to continue your site configuration on the Site to Site Topology tab as described in Configure site to site topology . Click the Next  icon. The ANAP tab appears if you are using an ANAP. The Site to Site Topology tab appears if you are not using an ANAP. Click Submit to send a change request with the entries made on this page to Aryaka support. Next steps Configure ANAP Information Configure site to site topology Related topics Site types overview Download a virtual ANAP image Configure Site to Site Topology Configure Routing Configure Advanced Settings