It is necessary to define a new Element Type for each OS type, for Single Connect to be able to auto-detect.
Ex: CentOS Linux, Ubuntu Linux, etc.

Follow the steps below to import AWS devices, having a specific OS created for each specific Element Type for that OS (The example below applies to CentOS).

Current element types can also be used instead of creating new element types for each device type. The Element type pattern should be set as the desired types like “

Learn how to create a new Element Type with specific operating systems in this document. By creating these Element Types, Single Connect can automatically detect the OS of discovered AWS instances. Set properties such as access protocol, OS pattern, SSH u

Creating AWS Accounts

Configuring Element Types

Creating AWS Device Import Jobs

Single Connect Reference Guide

3.2.0 Single Connect Web GUI

License Manager

Email Server Configuration

Mail Management

Language Settings

Menu Lists Management

System Configuration Parameters

Enabling Push Notifications for Mobile Application

Backup Manager

Enabling HTTPS on the Single Connect Web GUI

802.1x Authentication

SAML Authentication

Hardware Security Module (HSM) Integration

Windows Authentication on the Single Connect GUI

Multitenancy

Single Connect Administration

Manual User Creation

Single Connect Users Search

User Definition Option Menu

Editing Single Connect Users

User Properties Set up 

Temporary User

Local User Bulk Import

New User Request

Force New User to Change Password 

User Password Strength Settings 

User Password Hash Algorithm Settings

Notifying Inactive Users Before Lock

LDAP/Active Directory Integration

User Group Creation

Assigned Credentials

SSH Keys Manager

User Management

Element Type

Device Groups

Device Inventory

Device Management

Policy Key Definition

Policy Groups Definition

Policy Realm Definition

Policy Tracking

Policy Management

Managerial Approval for Connections 

Managerial Approval Reservation

Managerial Approval for Commands

Managerial Approval in Shared Account Password Manager (SAPM)

Approval Workflow

Approval Workflow SMS Settings

Approval Management

SSH Proxy

RDP Proxy

HTTP Proxy

Advanced Authorization Methods

Threat Analytics

Session Manager

Shared Accounts Password Management (SAPM)

Managing Application-to-Application Password Management (AAPM) Accounts

Password Vault

Sending MFA QR Code to Users

Creating a Connection Between Single Connect and the Single Connect Mobile Application

Enabling Multi Factor Authentication (MFA)

Using MFA to Log in to the Single Connect Web GUI

Using MFA to Log in to the Single Connect Desktop Client

Using MFA for SSH Connections

Using MFA for RDP Connections

Using MFA for SSH Proxy

Using MFA for HTTP/HTTPS Proxy

Using MFA for SFTP Proxy

Using MFA for TACACS+ Manager

Using MFA for Radius

Using MFA for Mobile Application

Offline/Online Mode Settings

Using SMS for MFA

Using Hardware Tokens for MFA

MFA Configurations for VPN Services

External MFA Providers

Multi-Factor Authentication

Basic Configurations for TACACS+ Devices

MSCHAPv2 RADIUS Configuration

TACACS+ Management Configuration Page 

TACACS+ Access Manager

SQL Proxy

Sensitive Data Discovery

SFTP Proxy

Data Access Manager

Importing Devices from Amazon Web Services

Importing Devices from Microsoft Azure

Importing Devices from Google Cloud Platform

Cloud PAM

Single Connect Logs

Active Sessions and Dual Control

System Log Viewer

Viewing Logs in Different Time Formats

Log Backup Management and Archiving

SIEM Configuration

Reports

Dashboard

Tamper Proof Logging

Single Connect Reporting and Logging Functions

Adding New Command Templates

Executing a Command Template

Adding a New Script

Running a Script

Creating a Workflow

Running a Workflow

Workflow History Logs

Privileged Task Automation Manager

Monitoring

Alarms

Alarm Configuration

Monitoring & Alarms

Watchdog Configuration 

Watchdog Mechanism

High Availability

Failover Scenario

Visualizing Reports and User Rights

Creating Charts for Reporting

Creating Dashboards

Report Email Scheduling

Dynamic Reports

Reporting

Logical Architecture

Tenant Management Requirements 

Tenant Management Interface

Administration by Tenant Admins

System Config Manager Parameters

DevOps Integration

APPENDIX 1: System Config Manager Parameters

APPENDIX 2: Job Descriptions for Job Scheduler

Reference Guide 

Parameter Name	Parameter Value
device.import.aws.access.protocol	Mandatory. This property is used to determine the default access method for the discovered instance.
device.import.aws.element.type.pattern	Mandatory. One element can have multiple patterns. This pattern is checked against the “AMI ID” description of the instance, in order to determine the OS type.
device.import.aws.ssh.username	Mandatory. This username is used as the default log in credential.
device.import.aws.port.number	Optional. Devices are imported with the defined port number value. If this value is not set, a default port number is used, such as 22 for SSH.
device.import.aws.ami.id	Optional. Exact AMI IDs should be defined. This property can be defined as multiple in one element. If this value is set, the exact AMI ID match is checked before the element type pattern (device.import.aws.element.type.pattern) match, when attempting to import devices.
device.import.aws.save.windows.admin.password	While importing Windows devices from AWS, the usernames and passwords will be retrieved from AWS by using a private key for zero touch onboarding. If the parameter is set as “true”, the credentials are stored in the “AdminCredentials-<$publicIPofdevice>” If this value is not set, the default value is “False”.