Configuring Element Types

it is necessary to define a new element type for each os type, for kron pam 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) navigate to devices > element type create a new element type add aws tag click the next button of the related element type fill these element type properties, so that kron pam can identify the os of the discovered instances aws element type pattern , aws access protocol , and aws ssh username properties field name parameter value aws access protocol mandatory this property is used to determine the default access method for the discovered instance 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 aws ssh username mandatory this username is used as the default log in credential 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 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) matches, when attempting to import devices 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>” sapm if this value is not set, the default value is “false” 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 “ linux|debian|ubuntu ”