/
Creating As-a-Service

Creating As-a-Service

For more information on NIOS-X as a Service, see NIOS-X as a Service.

It is recommended that you pre-create the Locations and Credentials (Pre-Shared Keys) that you will use for each of your remote sites (Access Locations) before configuring the Service Deployment. In order to use a Location when setting up an Access Location, you must set at least a Country and a Post Code. The UI will filter out any location that has just Latitude/Longitude information.

To create a service, complete the following:

  1. Go to Configure > Service Deployment > As-A-Service

  2. At the bottom of the Services pane, click Add Service.

  3. Configure the following in the General tab:

    • Name: Specify a name for the service.

    • Description: Provide a brief description.

    • Tags: Click Add and specify the Key and Value. You can add a maximum of 50 tags. For information about tags, see Managing Tags.

    • Capabilities: Choose one or more protocol services:

      • DHCP - choose the policy from the drop-down and confirm the selection by clicking the checkmark. By default, the Global Policy is selected. For more information, see Configuring Global DHCP Properties. If you want to use a custom policy, you can configure a DHCP Config Profile and choose the custom policy. For more information, see Configuring DHCP Config Profiles.

      • DNS - choose the policy from the drop-down and confirm the selection by clicking the checkmark. By default, the Global Policy is selected. For more information, see Configuring Global DNS Properties. If you want to use a custom policy, you can configure a DNS Config Profile and choose it as a custom policy.

      • NTP - choose this option if you want NIOS-X as a Service to sync the time with the Global NTP Settings. NTP (Network Time Protocol) is a standard protocol that system clocks use to ensure their time is always accurate. Servers that use NTP try to synchronize their time as close as possible to UTC (Coordinated Universal Time), the standard timescale used worldwide. For communications between clients and servers, NTP uses UDP (User Datagram Protocol) on port 123. The NTP capability only allows using the Global NTP Settings. For more information, see Configuring Global NTP Settings.

      • Security - The Security capability is only available if DNS capability is added. Choose the policy from the drop-down and confirm the selection by clicking the checkmark. The default global policy is selected by default. If you want to use a custom policy, you can configure a custom Security Policy. For more information, see Creating Security Policies.

NOTE: When you add a Capability to a service, you must click the small blue checkmark to the right of the Capability's drop down box option to save that Capability in the service. If you do not, then when you click the Save button, the service will not retain that Capability.

Click the blue checkmark to the right of the Capability, to save the Capability to the service.
Image: Click the blue checkmark to the right of the Capability, to save the Capability to the service.

 

  1. Click the Deployment tab. Click Add Service Deployment. Configure the following tab:

    • Name: Specify a name for the deployment.

    • Deployment Type: As a Service is selected by default.

    • Configure the following in the Service Location pane:

      • Size: This is the maximum number of Access Locations supported in a service deployment. Choose one of the following sizes:

        • S (Supports 10 locations)

        • M (Supports 20 locations)

      • Use Recommended Location: Select the check box to use the service location recommended by NIOS-X-as-a-Service based on position of the access location(s). For example, if the access location is Mumbai, choosing this check box allows NIOS-X-as-a-Service to choose the Point of Presence (PoP) that is the closest, which in this case is AWS Asia Pacific. If you create two access locations, selecting this check box will allow NIOS-X-as-a-Service to choose the PoP that is closest to both. This option can be selected only when creating a service. 

      • Location: Choose one of the Available Locations. This option is disabled if you have selected the Use Recommended Location option.

      • Service IP: Specify a single private IP address that the services (DNS/DHCP/Security) will run on. This is the IP address that clients on your network will send DNS/DHCP traffic to. It is recommended to use an IP address which is not being actively used in your network. The following IP addresses are not allowed: 169.254.0.0/16, 172.31.0.0/16.

      • Primary Neighbor IP: Specify the IP that that will be used as the source IP when the Service Location initiates traffic to on-prem (for example, forwards a DNS request from the POP to a DNS server that is on-prem).

      • Secondary Neighbor IP: Specify the IP that that will be used as the source IP when the Service Location initiates traffic to on-prem  (for example, forwards a DNS request from the POP to a DNS server that is on-prem). This is the backup of the Primary Neighbor IP as it exists in a separate availability zone in the POP.

      • Alternative Access Location: If you would like to provide an alternate IP address for managed service, toggle Alternative Access Location and specify the IP address.

      • Tags: Click Add and specify the Key and Value. You can add a maximum of 50 tags. For information about tags, see Managing Tags.

    • Configure the following in the Access Locations pane:

      • Type: Choose if the type is a Site or an AWS Cloud VPC.

      • Site: Click Select to add Site. Choose Existing to select an existing site from the drop-down. Alternatively, choose New to create a new Site by specifying the following:

        • Name: Specify the name of the Site.

        • Country: Select the country from the drop-down. Alternatively, you can also specify the Postal Code.

        • Postal Code: Specify the Postal Code. If you specify a valid Postal Code, the address, including country is entered automatically.

        • Contact: Expand the Contact section to enter Contact Name, Email, and Phone details.

      • Credential: Click Add to add the pre-shared key (PSK) credential. Choose Existing to select an existing PSK credential from the drop-down. Alternatively, choose New to create a new PSK credential by specifying the following:

        • Name: Specify the name of the credential.

        • Description: Provide a brief description.

        • Pre-shared Key: Specify a pre-shared key.

        • Tags: For information about tags, see Managing Tags.

      • WAN IP Addresses: Specify one or two WAN IP addresses. This is a public IP of your Internet facing gateway (Router/Firewall). A maximum of two IP addresses are allowed separated by a comma. The following IP addresses are not allowed: 169.254.0.0/16, 100.64.0.0/10.

      • Custom Network Attributes: Click Manage. Specify the LAN Subnets. This must be a private IP subnet that needs to communicate with NIOS-X as a Service. You can specify multiple subnets separated by comma. Click Add. The following subnets are not allowed: 169.254.0.0/16, 100.64.0.0/10, 172.31.0.0/16.

      • Click Apply after configuring the access locations. To make changes in the access location after applying, expand the access location tree and hover on the site name and click to perform edit/delete of the access location.

    • Tags: Click Add and specify the Key and Value. You can add a maximum of 50 tags. For information about tags, see Managing Tags.

    • Click Add to complete a service deployment configuration.

    • Click to edit any parameters of service deployment or delete service deployment.

    • To add multiple service deployment click Add Service Deployment.

    • Click Save to save the newly created service.

The Service IP, Primary Neighbor IP and Secondary Neighbor IP are independent /32 IP addresses. It is recommended (but not mandatory) that the IP addresses be unique across all your service deployments. The Primary Neighbor IP is accessible only via the primary VPN tunnel. The Secondary Neighbor IP is accessible only via the secondary VPN tunnel. The Service IP is accessible via both primary and secondary VPN tunnels.