Can I Install my Network Connector in AWS?

To deploy your Network Connector in your AWS account you need:

Pre-requisites

• Your own VPC
• Internet GW. The network connector will establish an outbound TLS connection where outbound traffic on ports 80 and 443 must be allowed
• Host instance with the appropriate OS (Linux or Windows). We recommend you:
  • Instance type/size: t2.medium or higher
  • For Windows OS:
    • Windows Server 2016 but other versions will work (see Network Connector requirements)
    • List of Windows AMIs: https://aws.amazon.com/windows/resources/amis/
  • For Linux OS:
    • The agent is supported on 64-bit platforms only, and is available in 2 variants:
      • *.rpm
        This generic RPM package is intended to support recent Enterprise Linux 7 based distros and newer.
        For example:
        • CentOS 7.0 and newer
        • Fedora 19+
        • RedHat Enterprise Linux 7.x and newer.
      • *.deb
        This generic DEB package is intended to support recent 64-bit Debian-based distros, in particular:
        • Ubuntu 15.04 and newer
        • Debian 8.0 (Jessie) and newer.
          Note: Asavie has not explicitly tested on all relevant distros. Testing so far for the *.rpm package has concentrated on CentOS 7 (Core) while for* .deb testing has concentrated on Ubuntu 16.04.3 LTS.

• • • List of Linux AMIs: here

• We recommend you also to set up a Security Group restricting inbound access from source IP of your office or the environment from where you’ll be managing your VPC via e.g. Remote Desktop.

Once your environment is ready you will need to:

1. Install the Network Connector
   1. Access to your Windows host through RDP
   2. Download the Network Connector Installer by copying the file through Remote Desktop or if you open your IoT Connect account from a browser in your Windows instance and download it form your account
   3. Run the installer and follow the steps (it will ask you for the activation code).
2. Setup the routing table with an entry for the subnet of your SIMs, which is set to the Network Interface of the Network Connector. This can be completed with the following CLI command:
   aws ec2 create-route –route-table-id [route id] –destination-cidr-block [IP range of your SIMs] –gateway-id [id of the network interface created by the Network Connector].
   More info here: http://docs.aws.amazon.com/cli/latest/reference/ec2/create-route.html
3. Disable Source and Destination checking which can be completed with the following CLI command:
   aws ec2 modify-instance-attribute –instance-id [id of your instance] –source-dest-check “{\”Value\”: false}.
   More info here: http://docs.aws.amazon.com/cli/latest/reference/ec2/modify-instance-attribute.html

 

…