<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=676831495802534&amp;ev=PageView&amp;noscript=1">


Getting Started with Intigua on AWS

1. Launch an Intigua server on the AWS Marketplace

  • Version: Latest Version
  • Security Group: The Intigua server should be able to receive TCP connections on port 443 (HTTPS), from both end-users and servers being managed. Additionally, for a simple deployment, managed servers should be reachable from the Intigua server on port 22 (for Linux servers) or 445 (for Windows servers).

2. Go to the Intigua Console via a browser at https://<hostname or IP>/

  • When you first access the Intigua Console, you will be asked to create an admin user with a strong password (at least 8 characters combining uppercase, numbers and symbols).
  • After creating this user, log into the console and accept the license.

3. Discover your AWS servers by setting up AWS integration

  • Go to Settings → Discovery Sources
  • Click “Add Discovery Source”

add_discovery_source.png \

  • Choose Source Type - Amazon EC2
  • Give a Source name
  • Enter an AWS Access key and Secret key for use in extracting the list of servers (follow the steps at this link). The AWS user entity should have ec2-describe-instances permission for all regions.
  • Choose which tags to import, if any. You can change this selection later.

4. Configure Intigua access to instances -> in the Settings tab, under Server Accounts. Click Edit Credentials to add new accounts.

  • For Linux instances - select Linux type, and upload your private key or password. Be sure to set the correct username - ec2-user for most Linux images on Amazon, root for some other images, ubuntu for some Ubuntu images, and centos for CentOS images. If you need to use several user names or private keys, define multiple server accounts. If not sure which username to use, you can find out through the AWS console:

  • For Windows instances using AWS-managed admin access, select AWS Windows type, and upload your private key. This will allow Intigua to query the AWS API for administrator passwords. Also set the username, which is typically Administrator but can also be the equivalent in other languages.
  • For Windows instances using a known user and password for remote access, select Windows type and enter the username and password.


5. Create a management service

  • Library Tab → Management Services
  • Select "Add Service"
  • Enter a Name and select a management tool from the drop-down list
  • Edit the management service properties- Managed Agent settings, Container settings, and Console settings.

* If the tool you need is not available in the drop-down list, you can add more tools by uploading an agent. In order to upload an agent to Intigua, it has to be in VAI format. VAI files are available from Intigua for various tools, and can also be created independently using Intigua’s self-service agent packaging tool. Contact support@intigua.com for details.


6. In order to manage Intigua on your servers go to the “Servers” Tab 

  • Select the servers you want to connect to Intigua
  • Click “server actions” → assign account → assign the account that matches your server
  • Click “server actions” again → “Manage Intigua on Server”
  • Intigua is now connecting to your server- this will take a moment
  • Once the process is complete, the green lightning icon will show up on the left.

 7.  To apply/remove management services click “server actions” once again → “apply/remove management services”

  • A window of all the tools will pop up
  • Choose the tools you wish to manage on the server

» You also can automatically assign accounts to all servers, and configure which agents need to be deployed to which servers, through the Policy tab, following these simple steps.

» Alternatively to providing Intigua with server access accounts for all servers, you can also embed the Intigua connector component into your AWS base images. To do so, follow the instructions in Intigua’s knowledge center.