​
1. Configure a Windows Instance on AWS to Run the On-Premise Data Gateway

​
1.1 Log in to the AWS Account for Setup

This account must have permission to launch EC2 instances. Enter the AWS console and then access the EC2 service (used to create remote instances on AWS).

​
1.2 Access EC2

In the resources section, click on ‘Instances (running)’ and check if there are two Nekt instances running. If they are not there or not running, contact Nekt. Click on ‘Launch instance’ to create a new instance, which will be the Windows instance to be used as a gateway. To configure the new instance:

  • Name and tags: you can choose any name that helps identify it, but we suggest power-bi-gateway.
  • Application and OS Images (Amazon Instance Image): in the Quick Start tab, select the Windows instance type. In ‘Amazon Instance Image (AMI)’, select ‘Microsoft Windows Server 2025 Base’ - usually the default.
  • Instance type: your use case might require a more powerful configuration, but a suggested minimum configuration is: Instance: t3.medium Price per hour: $0.06 vCPU: 2 memory: 4 GiB
  • Key pair: to access the instance via SSH, you need to select a Key Pair. If there isn’t an existing one you already use, you can create a new one by clicking ‘Create new key pair’. The generated file will be used later.
  • Network Settings: select ‘Create security group’ and ‘Allow RDP traffic from’ indicating the Nekt VPN IP (Custom > [3.215.86.80/32])
  • Configure Storage: Consider 1x 30 GiB gp3 Root Volume Click ‘Launch instance’.

Access the newly created instance in EC2. Click on the Connect option (or, from the menu, ‘Actions’ > ‘Connect’) and go to the RDP Client tab. Here, we’ll get the information needed to run the instance in RDP (Microsoft Remote Desktop application, indicated in the next section). - Public DNS - Username - Password (you must generate a Password in ‘Get Password’, but this option becomes available after at least 4 minutes from instance creation) - Private key: upload the file generated when creating the key pair. - Click ‘Decrypt password’ and it will generate the password to be used in RDP.

​
1.3 Access Microsoft Remote Desktop (RDP)

Install the Microsoft Remote Desktop application and follow the steps below to add the virtual instance. 1. Click on Add a new PC - PC name: paste the Public DNS copied earlier - User Account: Click on Add User Account - Username: paste the Username copied earlier - Password: paste the Password copied earlier - Friendly name: enter an arbitrary, friendly, and intuitive name for this user being created - With the newly created User Account selected, click ‘Add’ 2. Connect to the new PC - Click on the newly added PC. In the popup that opens, click ‘Continue’ - The new computer will open in full screen and initialize

Now we have a Windows instance running in the AWS cloud to serve as a Connection Gateway. Inside this instance, install the latest version of Power BI Desktop and the latest version of On-Premises Data Gateway.

In the PowerBI installed on this instance, we suggest configuring it to use the Nekt connector documented here, in order to test its functionality.

Then, just follow the step-by-step guide for connecting the connector using a gateway.

If you encounter any difficulties, contact our support and we’ll help you!