# 3  N2WS Server Instance Configuration

## 3.1  N2WS Server Instance Connectivity

For the configuration process to work, as well as N2WS’s normal operations, N2WS needs to be able to “talk” with AWS APIs. Thus, it needs to have outbound connectivity to the Internet.&#x20;

Verify that the N2WS instance has Internet connectivity; this can be achieved by placing the instance in a public subnet with a public IP address, by assigning an Elastic IP to the instance, using a NAT instance, or by using the Internet Gateway. You also need to make sure DNS is configured properly and that HTTPS protocol is open for outbound traffic in the VPC security group settings. It is by default.

## 3.2  Creating an Instance When Launching through EC2

1.  Under the **Name and tags** section, enter a name for your instance in the **Name** box.

    If required, select **Add additional tags.**

<figure><img src="https://3269456955-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68BQdax7IvSxhVLJ4IgD%2Fuploads%2FUaa96mXQh7qE8qv5VSIS%2Fname-and-tags.png?alt=media&#x26;token=5683282e-7971-4653-895a-f0235ec56723" alt=""><figcaption></figcaption></figure>

&#x20; 2\.  Under **Application and OS images (Amazon Machine Image)**, leave all default values, as this section shows what AMI we are using for the EC2 instance image.

<figure><img src="https://3269456955-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68BQdax7IvSxhVLJ4IgD%2Fuploads%2FaRJE08EMatiuPQOvJvwY%2FAMI.png?alt=media&#x26;token=768f4b8a-a78f-48b9-bb42-2b3c1375a426" alt=""><figcaption></figcaption></figure>

&#x20; 3\.  Under **Instance type**, the recommended minimum size is **t3.medium**. However, for bigger environments, the type may need to be larger.

{% hint style="info" %}
For information on choosing the appropriate size, see [https://support.n2ws.com/portal/en/kb/articles/recommended-instance-sizes-for-cpm-server-instances](https://support.n2ws.com/portal/en/kb/articles/recommended-instance-sizes-for-cpm-server-instances)
{% endhint %}

<figure><img src="https://3269456955-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68BQdax7IvSxhVLJ4IgD%2Fuploads%2FZW3Z7cGGifnT8Nj6nMoo%2FInstance-type.png?alt=media&#x26;token=16f88a87-b2fd-4232-9660-a9576057b11d" alt=""><figcaption></figcaption></figure>

4\.  Under **Key pair**, you can create a new key pair or use an existing one. The key pair is used when connecting to the instance’s CLI.

<figure><img src="https://3269456955-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68BQdax7IvSxhVLJ4IgD%2Fuploads%2FkN1aqOjALEXITbe5wWPa%2Fkey-pair.png?alt=media&#x26;token=39829ae2-f959-4fd7-97aa-efd681e3c01f" alt=""><figcaption></figcaption></figure>

&#x20; 5\.  Under **Network settings**, select a relevant **VPC**, **Subnet**, and **Security group** for the instance. For the configuration process to work, as well as for normal N2WS operations, N2WS needs outbound connectivity to the Internet for the HTTPS protocol. Needed are:

* A public IP, or
* An Elastic IP attached to the instance, or
* Connectivity via a NAT setup, Internet Gateway, or HTTP proxy,

<figure><img src="https://3269456955-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68BQdax7IvSxhVLJ4IgD%2Fuploads%2FvzMYNHQglmaTHgRAfbpw%2FNetwork-settings.png?alt=media&#x26;token=fe90446e-8c47-4c4c-a82b-b7dfed19d59d" alt=""><figcaption></figcaption></figure>

&#x20; &#x36;**.**   Under **Configure storage**, keep the Root volume as 30GB, but change the volume type to General Purpose SSD **(GP3).** You can also encrypt the volume with a default or custom managed KMS key.

<figure><img src="https://3269456955-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68BQdax7IvSxhVLJ4IgD%2Fuploads%2FgCPEOe11pP0vYniLpX71%2FConfigure-storage.png?alt=media&#x26;token=497e3d24-1600-4606-ae14-63617d42f058" alt=""><figcaption></figcaption></figure>

&#x20; 7\.  Under **Advanced details**, the only mandatory field to change is the IAM instance profile. Create a new role to give the EC2 instance the minimum permissions needed to perform its functions. See [https://support.n2ws.com/portal/en/kb/articles/what-are-the-required-minimal-aws-permissions-roles-for-cpm-operation](https://support.n2ws.com/portal/en/kb/articles/what-are-the-required-minimal-aws-permissions-roles-for-cpm-operation)

&#x20; 8\.  Select **Launch instance.**

## 3.4 N2WS Server Instance Configuration

{% hint style="info" %}
For N2WS to work, JavaScript needs to be enabled on your browser.
{% endhint %}

N2WS has a browser-based management console. N2WS supports Mozilla Firefox, Google Chrome, and Safari.

After launching the N2WS AWS instance, use the AWS Management Console or any other management tool to obtain the address of the new instance:

![](https://content.gitbook.com/content/68BQdax7IvSxhVLJ4IgD/blobs/XAbm9sUUg0fGwrgWI3bO/3-2%20config%20new%20instance.png)

{% hint style="info" %}
Use the address provided to you by N2WS to connect to the N2WS Server using the HTTPS protocol in your browser (`https://<server address>`).
{% endhint %}

When a new N2WS Server boots for the first time, it will automatically create a self-signed SSL certificate. After the initial configuration, it is possible to upload a different certificate. Since the certificate is unique to this server, it is perfectly safe to use. However, since the certificate is self-signed, you will need to approve it as an exception for the browser. To add an exception for the default certificate in Chrome and Firefox, see [Appendix B – Adding Exception for Default Browser.](appendix-b-adding-exception-for-default-browser)

After adding the exception, you get the first screen of the N2WS configuration application.

## 3.3  N2WS Server Configuration Wizard

The N2WS Server Configuration wizard takes you through the process step by step. There are a few differences between configuring N2WS for the Free Trial and other paid editions.&#x20;

#### For the N2WS Free Trial Edition:

* A new volume must be defined for the N2WS server.
* You will need to enter a user name, a valid email address, and enter a password and verify it.

#### For other N2WS Editions:

### **Step 1: Verify ownership of new instance**

On the first screen, you will be asked to type or paste the instance ID of this new N2WS instance. This step is required in order to verify that you are indeed the owner of this instance.

![](https://content.gitbook.com/content/68BQdax7IvSxhVLJ4IgD/blobs/HOoudNgMcryJPNOhEbFN/3-3%20config%20step%201.png)

Select **Next**. In the next step, the N2WS configuration procedure begins.

### **Step 2: Approve the N2WS license agreement**

Review the end-user license terms, select the acceptance checkbox, and select **Next**.

![](https://content.gitbook.com/content/68BQdax7IvSxhVLJ4IgD/blobs/iVuIM7nPgkohRqj0hEe8/3-3%20config%20step%202.png)

### **Step 3: Configure the license type, N2WS “root” account password, and user information**

![](https://content.gitbook.com/content/68BQdax7IvSxhVLJ4IgD/blobs/bpckWkxf94ToVsB75Bbg/3-3%20config%20step%203.png)

For the Free Trial, leave the **License** list with the defaul&#x74;**.** If you purchased a license directly from N2W Software, choose one of the **License** options, according to the instructions you received.

{% hint style="info" %}
If anyone in your organization already installed an N2WS Free Trial in the past on the same AWS account, you may receive an error message when trying to configure or connect to N2WS. Contact [support@n2ws.com](mailto:support@n2ws.com) to resolve.

If you are using one of the N2WS paid products on AWS Marketplace, you will not see the License field.
{% endhint %}

If this is an upgrade, the username must remain as it was prior to the upgrade, but the password can be modified.

{% hint style="info" %}
Passwords: N2WS does not enforce password rules. However, it is recommended that you use passwords that are difficult to guess and to change them regularly.
{% endhint %}

When you have completed entering the details for Step 3, select **Next**.

### **Step 4: Time zone, new volume, force recovery mode, and web proxy settings**

![](https://content.gitbook.com/content/68BQdax7IvSxhVLJ4IgD/blobs/1GGDzfRG2kX1dH8iqfaw/3-3%20config%20step%204.png)

1. Choose your time zone.
2. If configuring a paid edition, choose whether to create a new data volume or use an existing one. To configure an additional N2WS server, in recovery mode only, choose an existing data volume and select **Force Recovery Mode**. In Step 5, you will be presented with a list of existing N2WS data volumes.

![](https://content.gitbook.com/content/68BQdax7IvSxhVLJ4IgD/blobs/o7roMz6X2tnNF4lVmFli/3-3%20config%20step%204a.png)

{% hint style="info" %}
**The N2WS server configured for recovery mode will&#x20;**_**NOT**_**:**

* Perform backups.
* Copy to S3.
* Have Resource Control management.
* Perform any scheduled operations.
{% endhint %}

&#x20;   3\. If you select **Enabled** for **Connect via Web proxy**, additional boxes appear for defining the proxy:

![](https://content.gitbook.com/content/68BQdax7IvSxhVLJ4IgD/blobs/Oj32mV4DO9S3dZw2KJnm/3-3%20config%20step%204b.png)

&#x20;   4\. Select **Next**.

### **Step 5: Data volume type and encryption, security settings, and anonymous usage reports**

1. If you are configuring a new data volume, you have an option to encrypt N2WS user data. Select **Encrypted** in the **Encrypt Volume** drop-down list and choose a key in the **Encryption Key** list. You have the option to use a custom ARN.

![](https://content.gitbook.com/content/68BQdax7IvSxhVLJ4IgD/blobs/DFa1ooIBc7CsXoQzBU97/3-3%20config%20step%205.png)

&#x20;   2\. If you chose to use an existing volume or selected **Force Recovery Mode** in Step 4, you will see a drop-down volume selection box.

![](https://content.gitbook.com/content/68BQdax7IvSxhVLJ4IgD/blobs/fKq2Bpq3wr3QEiEoxuFM/3-3%20config%20step%205a.png)

&#x20;   3\. Complete the Web Server settings. The default port 443 is used by the N2WS manager.

&#x20;   4\. Allowing anonymous usage reports will enable N2WS to improve the product. The usage reports are sent to N2WS with no identifying details in order to maintain customer anonymity. You can disallow the anonymous reports at a later time in the N2WS **General Settings** menu.

&#x20;   5\. Select **Next** when finished.

### **Step 6: Register the account with N2WS**

![](https://content.gitbook.com/content/68BQdax7IvSxhVLJ4IgD/blobs/eGWEutiOmAOQPk4TJHBS/3-3%20config%20step%206.png)

**Registration is mandatory for free trials** and optional for paid product&#x73;**.** N2WS recommends that all customers register, as it will enable us to provide faster support. N2WS guarantees not to share your contact information with anyone.

If you have a Reference Code, enter it in the **Ref Code** box.

{% hint style="info" %}
**WARNING**: Use English characters only in registration. Non-English characters (e.g. German, French) will cause the operation to fail.
{% endhint %}

Select **Configure System** when finished. The Configuring Server message appears.

![](https://content.gitbook.com/content/68BQdax7IvSxhVLJ4IgD/blobs/N3kdWDRyMdVX2KSxKYSq/3-3%20config%20step%206a.png)

The registration and configuration process may take a while, after which a ‘Configuration Successful – Starting Server …’ message appears. It will take a few seconds for the application to start.

{% hint style="info" %}
If, for any reason, you are not directed automatically to the application login screen, reboot the instance from the management console.
{% endhint %}

![](https://content.gitbook.com/content/68BQdax7IvSxhVLJ4IgD/blobs/Wqrh6tHrW4qTTjc82JWO/3-3%20config%20step%206b.png)

You are now ready to log on with the credentials you created in the first screen and begin using N2WS. Selecting **Sign in with** **Identity Provider** will redirect you to the organization’s IdP system using SAML.

{% hint style="info" %}
Logging on for the first time with a trial edition can take up to 5 minutes as N2WS must connect and get approved by our licensing service.
{% endhint %}

The “Please wait …” message should go away in a few minutes. Allow 4-5 minutes and then refresh the screen.
